Amazon ECR now supports global authentication tokens for private registries
Share
Services
Amazon Elastic Container Registry (Amazon ECR) now supports global authentication tokens for private registries. Previously, you needed to request a separate authentication token in each AWS Region where you push or pull container images. Now, you can request a single token from the AWS Sign-In CreateBearerToken API and use it across all ECR private registries in the same AWS partition. Teams that run proxy services to route container pulls across Regions, a common pattern for optimizing latency or availability, previously had to request, refresh, and coordinate a separate token for every Region behind the proxy. With global tokens, the proxy manages one token for all Regions in the AWS partition. Global tokens are valid for 12 hours by default, but can be configured to be as low as 5 minutes. These tokens work with the Docker CLI, and the Amazon ECR Docker Credential Helper. Existing regional authentication tokens continue to work as before. Global authentication tokens are available in all commercial AWS Regions where Amazon ECR is supported. To learn more, see Private registry authentication in the [Amazon ECR User Guide](https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry%5Fauth.html).
What else is happening at Amazon Web Services?
Read update
Services
Share
Read update
Services
Share
AWS Security Hub now infers resource criticality from installed software and usage
about 23 hours ago
Services
Share