Amazon Elastic Container Registry (ECR) now supports PrivateLink for endpoints that have been validated under the Federal Information Processing Standard (FIPS) 140-3 program.
With this release, customers with security and compliance requirements can now use FIPS-validated cryptographic modules when connecting to Amazon ECR while keeping their traffic within their Amazon Virtual Private Cloud (VPC). This enhancement enables you to meet regulatory compliance requirements while maintaining the security benefits of private connectivity.
Support for PrivateLink for FIPS ECR endpoints is now available in (US East) N. Virginia, Ohio, (US West) N. California, Oregon and select (AWS GovCloud) US West and (AWS Govcloud) Us East regions. To learn more about AWS PrivateLink, see accessing AWS services through AWS PrivateLink. To learn more about FIPS 140-3 at AWS, visit FIPS 140-3 Compliance. You can learn more about storing, managing and deploying container images and artifacts with Amazon ECR, including how to get started, from our product page and user guide.
Categories: general:products/amazon-ecr,general:products/aws-govcloud-us,marketing:marchitecture/containers
Source: Amazon Web Services
Latest Posts
- Amazon Braket now in scope for FedRAMP Class C
- Workers, Cloudflare CLI – Test Cron Triggers with Local Explorer
- MC1191578: Exchange Online Pauses EWS Access Block for Kiosk and Frontline Worker Licenses
- Amazon CloudWatch log centralization now available in AWS GovCloud and additional commercial Regions
