How Company 3 Streamlines Studio Image Management with EC2 Image Builder and AWS CDK

Company 3, a powerhouse in post-production for major film and television studios, faced a challenge that many media companies encounter: managing consistent, reliable machine images across their global infrastructure. Their teams—scattered across multiple regions and working on everything from color grading to visual effects—needed standardized environments that could scale quickly without manual configuration creep. The solution came from combining two AWS services that don’t always get the spotlight together: EC2 Image Builder for automating image creation and AWS CDK for infrastructure as code. What emerged was a streamlined pipeline that reduced their image management overhead while improving consistency across their sprawling production infrastructure.

At its core, the approach works like this: EC2 Image Builder handles the heavy lifting of building and testing machine images automatically. Instead of manually installing software, configuring settings, and testing each time they need a new image, Company 3 defined their image requirements in code. They specify base operating systems, software packages (rendering tools, color correction software, codec libraries), security patches, and custom configurations. EC2 Image Builder then orchestrates the entire process—spinning up temporary instances, applying the specifications, running validation tests, and finally producing ready-to-use AMIs (Amazon Machine Images). AWS CDK, meanwhile, provided the glue. Using CDK’s Python constructs, their engineering team wrote infrastructure code that orchestrates the image building pipeline, manages dependencies, and handles the deployment of those images to their EC2 instances. This meant they could version control their entire image definition alongside their infrastructure, catch configuration errors before they hit production, and reproduce images consistently months or years later.

The practical benefits became clear quickly. When a security patch needed to roll out, the team no longer faced the choice between manual updates (slow and error-prone) or rebuilding from scratch (time-consuming). Instead, they triggered their CDK pipeline, which instructed EC2 Image Builder to create a new image with the patch applied, automatically tested it for their specific workloads, and made it available for deployment. For a studio working on tight production schedules—where a rendering node that crashes costs money by the hour—this reliability matters enormously. They also gained auditability. Every image version, every component version, every configuration change lived in their code repository with commit history. If an issue arose in production, they could trace it back to exactly when it was introduced and by whom.

What makes this approach particularly valuable for organizations like Company 3 is that it removes friction from infrastructure management without requiring deep AWS expertise from every engineer. The initial setup requires someone comfortable with CDK and image building, but once established, the pipeline becomes a reliable service that their teams can trigger and trust. It’s the difference between infrastructure as a bottleneck and infrastructure as an enabler—freeing their engineers to focus on what actually matters for their clients: delivering exceptional creative work on schedule.