Amazon ECR now supports PrivateLink for FIPS Endpoints

Amazon ECR PrivateLink FIPS Endpoints

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.

What to do

• Review the AWS PrivateLink documentation to understand how to access AWS services through AWS PrivateLink.
• Visit the FIPS 140-3 Compliance page to learn more about FIPS 140-3 at AWS.
• Explore the Amazon ECR product page and user guide to learn more about storing, managing, and deploying container images and artifacts with Amazon ECR.

Source: AWS release notes

If you need further guidance on AWS, our experts are available at AWS@westloop.io. You may also reach us by submitting the Contact Us form.