Amazon Elastic Container Registry (ECR) now supports ECR-to-ECR pull through cache
Amazon Elastic Container Registry (ECR) now supports ECR-to-ECR pull through cache, a capability that allows customers to automatically sync container images between ECR private registries existing across accounts and the Amazon Web Services China (Beijing) Region, operated by Sinnet and the Amazon Web Services China (Ningxia) Region, operated by NWCD. This enables customers to benefit from the reduced latency of pulling cached images in-region. With today’s release, Amazon ECR makes it easier for customers to optimize storage costs by providing a way to store local copies of only the images that are pulled across regions and accounts.
As customers grow, they often have container deployments spread across the Amazon Web Services China (Beijing) Region, operated by Sinnet and the Amazon Web Services China (Ningxia) Region, operated by NWCD. Storing images within the region of deployment improves application startup times due to lower latency of in-region pulls. To achieve this, customers have to maintain copies of all images in every region, which is not cost-effective as many of these images are not deployed. ECR-to-ECR pull through cache allows customers to sync images between ECR registries in a cost-effective way by caching only the images that are pulled. Customers can now push images to their primary registry and configure pull through cache rules to cache images into downstream registries. On an image pull, ECR automatically fetches the image from the upstream registry, and caches it into an automatically created repository in the downstream registry for future pulls. Additionally, this feature supports frequent syncs with the upstream registry, helping keep the cached images up to date.
ECR-to-ECR pull through cache is available in the Amazon Web Services China (Beijing) Region, operated by Sinnet and the Amazon Web Services China (Ningxia) Region, operated by NWCD. To learn more, visit the user guide.