Amazon Elastic Container Registry (Amazon ECR) pull through cache now supports Chainguard’s registry as an upstream source. With today’s release, customers now benefit from the security and availability of Amazon ECR for private Chainguard images.
As customers continue to scale their use of Chainguard images, keeping them synchronized with Chainguard’s registry becomes increasingly important. With ECR’s pull through cache feature, customers can keep Chainguard images in sync without additional workflows or tools to manage. Amazon ECR’s pull through cache supports frequent registry syncs, helping to keep container images sourced from Chainguard up to date. Later, customers can apply ECR features such as image scanning and lifecycle policies to their cached Chainguard images.
The pull through cache for Chainguard is available in all AWS Regions where Amazon ECR pull through cache is supported. To get started, review our documentation.
Categories: general:products/amazon-ecr,marketing:marchitecture/containers
Source: Amazon Web Services
Latest Posts
- Workflows – Rollback support now available in Workflows
- OneDrive: Retention enforcement for unlicensed OneDrive accounts [MC1381110]
- Microsoft Teams: Improved app and agent access request flows for admin‑blocked apps [MC1381120]
- (Updated) Upcoming change: disabling Teams meeting recording expiration notification emails [MC1245635]
