Organizations in regulated industries such as financial services, healthcare, government, and defense often manage their container registries in air-gapped AWS environments. These are Amazon Virtual Private Cloud (VPC) environments with no internet gateway and no NAT gateway, which organizations isolate to meet strict regulatory and security requirements. The isolation is the point: it helps organizations shrink their attack surface and keep sensitive workloads away from the public internet. That isolation also creates a practical problem.
Before a single application can run, infrastructure teams need to bring every dependency inside the boundary. For a typical Kubernetes environment, that means migrating dozens to hundreds of Helm charts and container images from public and private source registries into a private Amazon Elastic Container Registry (Amazon ECR) . And it isn’t enough to copy the artifacts across. Teams need to configure each repository to enforce the same security controls: encryption with customer-managed keys, immutable image tags, enhanced scanning, and lifecycle rules.
We saw this firsthand on an engagement with a European financial services institution operating under strict regulatory requirements. The hard part wasn’t any single repository. It was doing this consistently, across a large and growing set of repositories, without the security posture drifting from one to the next. That’s a design problem, not a scripting problem, and it is the problem this post is about. In this post, we walk through an approach that uses Amazon ECR repository creation templates, infrastructure as code with Terraform , and a migration tool to make secure-by-default the path of least resistance.
Although this post is structured as a technical how-to, it focuses on architectural decisions and trade-offs rather than step-by-step deployment. The sample repository linked at the end provides the full implementation. We assume familiarity with Amazon ECR, Terraform, and container orchestration with Kubernetes. The instinct when facing a one-time migration is to script it: pull each image, push it to a repository you created by hand, and move on. That works for a handful of repositories. It breaks down well before you reach a hundred, and it breaks down in ways that matter most in regulated environments.
