Amazon Elastic Container Registry (Amazon ECR) now automatically discovers and syncs OCI referrers, such as image signatures, SBOMs, and attestations, from upstream registries into your Amazon ECR private repositories with its pull through cache feature.
Previously, when you listed referrers on a repository with a matching pull through cache rule, Amazon ECR would not return or sync referrers from the upstream repository. This meant that you had to manually list and fetch the upstream referrers.
With today’s launch, Amazon ECR’s pull through cache will now reach upstream during referrers API requests and automatically cache related referrer artifacts in your private repository. This enables end-to-end image signature verification, SBOM discovery, and attestation retrieval workflows to work seamlessly with pull through cache repositories without requiring any client-side workarounds.
This feature is available today in all AWS Regions where Amazon ECR pull through cache is supported. To learn more, visit the Amazon ECR documentation.
Categories: general:products/amazon-ecr,marketing:marchitecture/containers
Source: Amazon Web Services
Latest Posts
- (Updated) Microsoft 365 admin center – Usage reports: Agent usage (preview) [MC1148545]
- AWS Marketplace introduces Tax management portal for sellers
- AWS Service Catalog is now available in the AWS Asia Pacific (New Zealand) and Canada West (Calgary) regions
- Amazon Route 53 Global Resolver now lets you add and remove AWS Regions for anycast DNS resolution
