If you've ever had a 2 AM page because a pod in ap-southeast-1 couldn't pull an image fast enough, or you've watched a deploy stall because your dev account is quietly trying to pull from a registry three regions away — you already understand the problem this post is about.
Amazon ECR is great at storing and serving container images. But the moment your infrastructure grows past "one region, one account," you run into a very familiar wall: images live in one place, and your workloads don't.
You could solve this with a cron job that pulls and re-pushes images on a schedule. People have done it. It works, right up until someone forgets to update the script, or a region gets missed, or you're debugging why staging has a stale tag at 11 PM on a Friday.
The better answer is ECR's built-in replication feature — and honestly, once it's set up, you mostly forget it's there, which is exactly what you want from infrastructure.
This guide walks through two real scenarios: replicating across regions, and replicating across accounts. Then we'll get into the production-readiness details that tend to get skipped in a first pass — because "it worked in the demo" and "it survives a security review" are two very different bars.
