Amazon ECR now supports pull through cache for Chainguard 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.

🆕 Amazon ECR now supports Chainguard’s registry as a pull through cache, enabling seamless synchronization of Chainguard images with ECR’s security and lifecycle features, available in all supported AWS Regions.

#AWS #AmazonEcr

Amazon ECR now supports pull through cache for Chainguard https://aws.amazon.com/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 ourhttps://docs.aws.amazon.com/AmazonECR/latest/userguide/pull-through-cache.html .

Amazon ECR now supports pull through cache for Chainguard

https://aws.amazon.com/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 Cha...

#AWS #AmazonEcr

Amazon ECR now supports additional metrics for monitoring repositories https://aws.amazon.com/ecr/ (ECR) now enables customers to monitor additional repository metrics through https://aws.amazon.com/cloudwatch/. These new metrics, RepositoryCount and ImagesPerRepositoryCount, help customers identify growth trends of images by repository as well as understand their trends for creating and deleting repositories. With these insights, customers can easily identify anomalous behavior and alert themselves when their usage approaches the service quota. These metrics are available in all AWS commercial and AWS GovCloud (US) Regions at no additional cost. To learn more about Amazon ECR repository metrics, please review our https://docs.aws.amazon.com/AmazonECR/latest/userguide/monitoring-usage.html.

Amazon ECR now supports additional metrics for monitoring repositories

https://aws.amazon.com/ecr/ (ECR now enables customers to monitor additional repository metrics through https://aws.amazon.com/cloudwatch/ These new metrics, RepositoryCount and ImagesPerRepositoryCount...

#AWS #AmazonEcr

Amazon ECR now supports cross-repository layer sharing to optimize storage and improve push performance Amazon Elastic Container Registry (ECR) now enables you to share common image layers across repositories within a registry through a capability called blob mounting. This feature is especially valuable if you manage multiple microservices or applications built from common base images. With blob mounting, you can achieve faster image pushes by reusing existing layers instead of re-uploading identical content, and reduce storage costs by storing common layers once and referencing them across repositories. Getting started is simple, enable the registry-level setting through the ECR console or AWS CLI. Once enabled, ECR automatically handles layer sharing when you push images. Blob mounting is available in all AWS commercial and AWS GovCloud (US) Regions. To learn more about blob mounting, please visit our https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry-settings.html.

Amazon ECR now supports cross-repository layer sharing to optimize storage and improve push performance

Amazon Elastic Container Registry (ECR) now enables you to share common image layers across repositories within a registry through a capability called blob mo...

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR now supports cross-repository layer sharing to optimize storage and improve push performance Amazon Elastic Container Registry (ECR) now enables you to share common image layers across repositories within a registry through a capability called blob mounting. This feature is especially valuable if you manage multiple microservices or applications built from common base images. With blob mounting, you can achieve faster image pushes by reusing existing layers instead of re-uploading identical content, and reduce storage costs by storing common layers once and referencing them across repositories. Getting started is simple, enable the registry-level setting through the ECR console or AWS CLI. Once enabled, ECR automatically handles layer sharing when you push images. Blob mounting is available in all AWS commercial and AWS GovCloud (US) Regions. To learn more about blob mounting, please visit our documentation.

🆕 Amazon ECR now enables cross-repository layer sharing with blob mounting, optimizing storage and push speed by reusing common layers across microservices, reducing costs, and speeding up pushes. Enable in ECR console or AWS CLI; available in all commercial and Gov…

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR now supports creating repositories on push Amazon Elastic Container Registry (ECR) now supports automatic repository creation on image push. This new capability simplifies container workflows by having ECR automatically create repositories if they don't exist when an image is pushed, without customers having to pre-create repositories before pushing container images. Now when customers push images, ECR will automatically create repositories according to defined repository creation template settings. Create on push is available in all AWS commercial and AWS GovCloud (US) Regions. To learn more about repository creation templates, please visit our https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-creation-templates.html. You can learn more about storing, managing and deploying container images and artifacts with Amazon ECR, including how to get started, from our https://aws.amazon.com/ecr/ and https://docs.aws.amazon.com/AmazonECR/latest/userguide/what-is-ecr.html.

Amazon ECR now supports creating repositories on push

Amazon Elastic Container Registry (ECR) now supports automatic repository creation on image push. This new capability simplifies container workflows by having ECR automatically create repositories if they don...

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR now supports creating repositories on push Amazon Elastic Container Registry (ECR) now supports automatic repository creation on image push. This new capability simplifies container workflows by having ECR automatically create repositories if they don't exist when an image is pushed, without customers having to pre-create repositories before pushing container images. Now when customers push images, ECR will automatically create repositories according to defined repository creation template settings. Create on push is available in all AWS commercial and AWS GovCloud (US) Regions. To learn more about repository creation templates, please visit our https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-creation-templates.html. You can learn more about storing, managing and deploying container images and artifacts with Amazon ECR, including how to get started, from our https://aws.amazon.com/ecr/ and https://docs.aws.amazon.com/AmazonECR/latest/userguide/what-is-ecr.html.

Amazon ECR now supports creating repositories on push

Amazon Elastic Container Registry (ECR) now supports automatic repository creation on image push. This new capability simplifies container workflows by having ECR automatically create repositories if they don...

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR now supports creating repositories on push Amazon Elastic Container Registry (ECR) now supports automatic repository creation on image push. This new capability simplifies container workflows by having ECR automatically create repositories if they don't exist when an image is pushed, without customers having to pre-create repositories before pushing container images. Now when customers push images, ECR will automatically create repositories according to defined repository creation template settings. Create on push is available in all AWS commercial and AWS GovCloud (US) Regions. To learn more about repository creation templates, please visit our documentation. 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.

🆕 Amazon ECR now auto-creates repositories on image push, simplifying container workflows. Available globally, this feature eases image management by eliminating the need for pre-repository creation. For details, see documentation.

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR Public now supports PrivateLink for US East (N. Virginia) SDK Endpoint Amazon Elastic Container Registry (ECR) Public now supports PrivateLink for the US East (N. Virginia) SDK endpoint, providing enhanced network security and private connectivity for customers. This update allows customers to access this ECR Public SDK endpoint through a private network connection, reducing exposure to the public internet. With this enhancement, customers can now establish a private connection from their Amazon Virtual Private Cloud (VPC) to their ECR Public SDK endpoint while creating and maintaining their ECR Public repositories. This means organizations can maintain network privacy and security, reduce exposure of sensitive network traffic, comply with stricter network security requirements, and simplify network architecture for accessing ECR Public resources. Get started today with the US East (N. Virginia) ECR Public SDK endpoint. To learn more, visit https://docs.aws.amazon.com/AmazonECR/latest/userguide/vpc-endpoints.html

Amazon ECR Public now supports PrivateLink for US East (N. Virginia) SDK Endpoint

Amazon Elastic Container Registry (ECR) Public now supports PrivateLink for the US East (N. Virginia) SDK endpoint, providing enhanced network security and private connectivity for customers. Thi...

#AWS #AmazonEcr

Amazon ECR Public now supports PrivateLink for US East (N. Virginia) SDK Endpoint Amazon Elastic Container Registry (ECR) Public now supports PrivateLink for the US East (N. Virginia) SDK endpoint, providing enhanced network security and private connectivity for customers. This update allows customers to access this ECR Public SDK endpoint through a private network connection, reducing exposure to the public internet. With this enhancement, customers can now establish a private connection from their Amazon Virtual Private Cloud (VPC) to their ECR Public SDK endpoint while creating and maintaining their ECR Public repositories. This means organizations can maintain network privacy and security, reduce exposure of sensitive network traffic, comply with stricter network security requirements, and simplify network architecture for accessing ECR Public resources. Get started today with the US East (N. Virginia) ECR Public SDK endpoint. To learn more, visit ECR documentation.

🆕 Amazon ECR Public now supports PrivateLink for US East (N. Virginia) SDK endpoint, enhancing network security with private connectivity, reducing public internet exposure, and simplifying secure access to ECR Public resources.

#AWS #AmazonEcr

Amazon ECR now supports managed container image signing Amazon ECR now supports managed container image signing to enhance your security posture and eliminate the operational overhead of setting up signing. Container image signing allows you to verify that images are from trusted sources. With managed signing, ECR simplifies setting up container image signing to just a few clicks in the ECR Console or a single API call. To get started, create a signing rule with an AWS Signer signing profile that specifies parameters such as signature validity period, and which repositories ECR should sign images for. Once configured, ECR automatically signs images as they are pushed using the identity of the entity pushing the image. ECR leverages AWS Signer for signing operations, which handles key material and certificate lifecycle management including generation, secure storage, and rotation. All signing operations are logged through CloudTrail for full auditability. ECR managed signing is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where AWS Signer is available. To learn more, visit the https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-signing.html.

Amazon ECR now supports managed container image signing

Amazon ECR now supports managed container image signing to enhance your security posture and eliminate the operational overhead of setting up signing. Container image signing allows you to verify that image...

#AWS #AmazonEcr #AwsGovcloudUs

Amazon ECR now supports managed container image signing Amazon ECR now supports managed container image signing to enhance your security posture and eliminate the operational overhead of setting up signing. Container image signing allows you to verify that images are from trusted sources. With managed signing, ECR simplifies setting up container image signing to just a few clicks in the ECR Console or a single API call. To get started, create a signing rule with an AWS Signer signing profile that specifies parameters such as signature validity period, and which repositories ECR should sign images for. Once configured, ECR automatically signs images as they are pushed using the identity of the entity pushing the image. ECR leverages AWS Signer for signing operations, which handles key material and certificate lifecycle management including generation, secure storage, and rotation. All signing operations are logged through CloudTrail for full auditability. ECR managed signing is available in all AWS Regions where AWS Signer is available. To learn more, visit the documentation.

🆕 Amazon ECR now offers managed container image signing for better security, easily set up via clicks or API. ECR signs images automatically using AWS Signer for key management, with all actions logged in CloudTrail. Available in all regions with AWS Signer.

#AWS #AmazonEcr #AwsGovcloudUs

Amazon ECR dual-stack endpoints now support AWS PrivateLink Amazon Elastic Container Registry (ECR) announces AWS PrivateLink support for its dual-stack endpoints. This makes it easier to standardize on IPv6 and enhance your security posture. Previously, ECR announced IPv6 support for API and Docker/OCI requests via the new dual-stack endpoints. With these dual-stack endpoints, you can make requests from either an IPv4 or an IPv6 network. With today’s launch, you can now make requests to these dual-stack endpoints using AWS PrivateLink to limit all network traffic between your Amazon Virtual Private Cloud (VPC) and ECR to the Amazon network, thereby improving your security posture. This feature is generally available in all AWS commercial and AWS GovCloud (US) regions at no additional cost. To get started, visit https://docs.aws.amazon.com/AmazonECR/latest/userguide/ecr-requests.html.

Amazon ECR dual-stack endpoints now support AWS PrivateLink

Amazon Elastic Container Registry (ECR) announces AWS PrivateLink support for its dual-stack endpoints. This makes it easier to standardize on IPv6 and enhance your security posture.

Previously, EC...

#AWS #AmazonEcr #AwsGovcloudUs

Amazon ECR dual-stack endpoints now support AWS PrivateLink Amazon Elastic Container Registry (ECR) announces AWS PrivateLink support for its dual-stack endpoints. This makes it easier to standardize on IPv6 and enhance your security posture. Previously, ECR announced IPv6 support for API and Docker/OCI requests via the new dual-stack endpoints. With these dual-stack endpoints, you can make requests from either an IPv4 or an IPv6 network. With today’s launch, you can now make requests to these dual-stack endpoints using AWS PrivateLink to limit all network traffic between your Amazon Virtual Private Cloud (VPC) and ECR to the Amazon network, thereby improving your security posture. This feature is generally available in all AWS commercial and AWS GovCloud (US) regions at no additional cost. To get started, visit ECR documentation.

🆕 Amazon ECR dual-stack endpoints now support AWS PrivateLink, allowing IPv6 requests and securing traffic within the Amazon network, enhancing security at no extra cost. Available in all commercial and GovCloud regions.

#AWS #AmazonEcr #AwsGovcloudUs

Amazon ECR introduces archive storage class for rarely accessed container images Amazon ECR now offers a new archive storage class to reduce storage costs for large volumes of rarely accessed container images. The new archive storage class helps you meet your compliance and retention requirements while optimizing storage cost. As part of this launch, ECR lifecycle policies now support archiving images based on last pull time, allowing you to use lifecycle rules to automatically archive images based on usage patterns. To get started, you can archive images by configuring lifecycle rules to automatically archive images based on criteria such as image age, count, or last pull time, or using the ECR Console or API to archive images individually. You can archive an unlimited number of images. Archived images do not count against your image per repository limit. Once the images are archived, they are no longer accessible for pulls, but can be easily restored via ECR Console, CLI, or API within 20 minutes. Once restored, images can be pulled normally. All archival and restore operations are logged through CloudTrail for auditability. The new ECR archive storage class is available in all AWS Commercial and AWS GovCloud (US) Regions. For pricing, visit the https://aws.amazon.com/ecr/pricing/. To learn more, visit the https://docs.aws.amazon.com/AmazonECR/latest/userguide/what-is-ecr.html.

Amazon ECR introduces archive storage class for rarely accessed container images

Amazon ECR now offers a new archive storage class to reduce storage costs for large volumes of rarely accessed container images. The new archive storage class helps you meet your co...

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR introduces archive storage class for rarely accessed container images Amazon ECR now offers a new archive storage class to reduce storage costs for large volumes of rarely accessed container images. The new archive storage class helps you meet your compliance and retention requirements while optimizing storage cost. As part of this launch, ECR lifecycle policies now support archiving images based on last pull time, allowing you to use lifecycle rules to automatically archive images based on usage patterns. To get started, you can archive images by configuring lifecycle rules to automatically archive images based on criteria such as image age, count, or last pull time, or using the ECR Console or API to archive images individually. You can archive an unlimited number of images. Archived images do not count against your image per repository limit. Once the images are archived, they are no longer accessible for pulls, but can be easily restored via ECR Console, CLI, or API within 20 minutes. Once restored, images can be pulled normally. All archival and restore operations are logged through CloudTrail for auditability. The new ECR archive storage class is available in all AWS Commercial and AWS GovCloud (US) Regions. For pricing, visit the pricing page. To learn more, visit the documentation.

🆕 Amazon ECR adds an archive class for cost-saving on rarely accessed container images, aiding compliance. Archive based on pull time, restore in 20 mins, and manage via lifecycle policies. Available globally; pricing on AWS pricing page.

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR now supports PrivateLink for 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. To learn more about AWS PrivateLink, see https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-access-aws-services.html. To learn more about FIPS 140-3 at AWS, visit https://aws.amazon.com/compliance/fips/. You can learn more about storing, managing and deploying container images and artifacts with Amazon ECR, including how to get started, from our https://aws.amazon.com/ecr/ and https://docs.aws.amazon.com/AmazonECR/latest/userguide/what-is-ecr.html.

Amazon ECR now supports PrivateLink for 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, customer...

#AWS #AmazonEcr #AwsGovcloudUs

Amazon ECR now supports PrivateLink for 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. 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.

🆕 Amazon ECR now supports AWS PrivateLink for FIPS 140-3 endpoints, enabling secure, compliant container image connections within VPCs in select regions.

#AWS #AmazonEcr #AwsGovcloudUs

Amazon Elastic Container Registry (ECR) now supports repository creation templates in the AWS GovCloud (US) Regions Amazon Elastic Container Registry (ECR) now supports repository creation templates in the AWS GovCloud (US) Regions. Repository creation templates allow you to configure the settings for the new repositories that Amazon ECR creates on your behalf during pull through cache and replication operations. These settings include encryption, lifecycle policies, access permissions, and tag immutability. Each template uses a prefix to match and apply configurations to new repositories automatically, enabling you to maintain consistent settings across your container registries. To learn more about ECR repository creation template, see our https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-creation-templates-create.html.

Amazon Elastic Container Registry (ECR) now supports repository creation templates in the AWS GovCloud (US) Regions

Amazon Elastic Container Registry (ECR) now supports repository creation templates in the AWS GovCloud (US) Regions. Repository creation templates...

#AWS #AmazonEcr #AwsGovcloudUs

Amazon Elastic Container Registry (ECR) now supports repository creation templates in the AWS GovCloud (US) Regions Amazon Elastic Container Registry (ECR) now supports repository creation templates in the AWS GovCloud (US) Regions. Repository creation templates allow you to configure the settings for the new repositories that Amazon ECR creates on your behalf during pull through cache and replication operations. These settings include encryption, lifecycle policies, access permissions, and tag immutability. Each template uses a prefix to match and apply configurations to new repositories automatically, enabling you to maintain consistent settings across your container registries. To learn more about ECR repository creation template, see our documentation.

🆕 Amazon ECR now supports repository creation templates in AWS GovCloud (US) for consistent settings like encryption, lifecycle policies, and permissions during cache and replication, enhancing container registry management.

#AWS #AmazonEcr #AwsGovcloudUs

Containers shouldn't complicate your workflow! 🎯 Our latest blog demystifies Amazon ECR, making your container management in AWS smoother, safer, and simpler.

Read the full blog: zurl.co/B2oqN

#Stormit #AWS #AmazonECR #DevOps

Amazon ECR enhanced scanning now surfaces image use status Amazon Elastic Container Registry (ECR) enhanced scanning now surfaces how an image is used on Amazon Elastic Kubernetes Service (EKS) and Amazon Elastic Container Service (ECS), including last used date, the number of clusters that the image was used, and the cluster ARNs. You can use this information to prioritize vulnerability remediation for images that are actively being used. ECR enhanced scanning is an integration with Amazon Inspector that provides vulnerability scanning for your container images. ECR enhance scanning scans your container images for both operating systems and programming language package vulnerabilities. With the launch today, you can understand whether and where your images are used on EKS and ECS. Using ECR or Inspector consoles and APIs, you can now identify when you last used an image, the number of clusters that the image was used, and which clusters are running the image with cluster ARNs. As the image use status changes, ECR enhanced scanning will continuously update the status and surface the new status as part of the enhanced scanning findings. ECR support for image use status is available for enhanced scanning customers at no additional cost and is generally available in all AWS Commercial and AWS GovCloud (US) Regions where enhanced scanning is available. To get started with ECR enhanced scanning, visit https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-scanning-enhanced.html.  

Amazon ECR enhanced scanning now surfaces image use status

Amazon Elastic Container Registry (ECR) enhanced scanning now surfaces how an image is used on Amazon Elastic Kubernetes Service (EKS) and Amazon Elastic Container Service (ECS), including last used date...

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR enhanced scanning now surfaces image use status Amazon Elastic Container Registry (ECR) enhanced scanning now surfaces how an image is used on Amazon Elastic Kubernetes Service (EKS) and Amazon Elastic Container Service (ECS), including last used date, the number of clusters that the image was used, and the cluster ARNs. You can use this information to prioritize vulnerability remediation for images that are actively being used. ECR enhanced scanning is an integration with Amazon Inspector that provides vulnerability scanning for your container images. ECR enhance scanning scans your container images for both operating systems and programming language package vulnerabilities. With the launch today, you can understand whether and where your images are used on EKS and ECS. Using ECR or Inspector consoles and APIs, you can now identify when you last used an image, the number of clusters that the image was used, and which clusters are running the image with cluster ARNs. As the image use status changes, ECR enhanced scanning will continuously update the status and surface the new status as part of the enhanced scanning findings. ECR support for image use status is available for enhanced scanning customers at no additional cost and is generally available in all AWS Commercial and AWS GovCloud (US) Regions where enhanced scanning is available. To get started with ECR enhanced scanning, visit ECR documentation.

🆕 Amazon ECR enhanced scanning now shows image use status on EKS and ECS, including last used date and cluster ARNs, helping prioritize vulnerability fixes for actively used images. Available at no extra cost in all AWS regions where enhanced scanning is supported.

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR expands registry policy to all ECR actions in AWS GovCloud (US) Regions Amazon Elastic Container Registry (Amazon ECR) now supports registry policy v2 in AWS GovCloud (US) Regions, allowing customers to manage IAM permissions for all ECR API actions and simplify ECR permission management. ECR registry policy allows customers to control usage of ECR private registries by granting permissions to perform registry-level actions to an AWS IAM principal. Registry policy version 1 (v1), only supported three actions: ReplicateImage, BatchImportUpstreamImage, and CreateRepository. Now, the new registry policy version 2 (v2) supports every ECR action. Using registry policy v2 makes it easier for customers to control permissions across all repositories in an ECR registry, allowing customers to improve security posture and save time versus configuring permissions individually across multiple repositories. To get started, customers can migrate from registry policy v1 to v2 using the ECR management console or with the new ECR https://docs.aws.amazon.com/AmazonECR/latest/APIReference/API_PutAccountSetting.html API. New ECR accounts automatically use registry policy v2. To learn more about ECR’s registry policy and permissions, see our https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry-permissions.html.

Amazon ECR expands registry policy to all ECR actions in AWS GovCloud (US) Regions

Amazon Elastic Container Registry (Amazon ECR) now supports registry policy v2 in AWS GovCloud (US) Regions, allowing customers to manage IAM permissions for all ECR API actions a...

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR expands registry policy to all ECR actions in AWS GovCloud (US) Regions Amazon Elastic Container Registry (Amazon ECR) now supports registry policy v2 in AWS GovCloud (US) Regions, allowing customers to manage IAM permissions for all ECR API actions and simplify ECR permission management. ECR registry policy allows customers to control usage of ECR private registries by granting permissions to perform registry-level actions to an AWS IAM principal. Registry policy version 1 (v1), only supported three actions: ReplicateImage, BatchImportUpstreamImage, and CreateRepository. Now, the new registry policy version 2 (v2) supports every ECR action. Using registry policy v2 makes it easier for customers to control permissions across all repositories in an ECR registry, allowing customers to improve security posture and save time versus configuring permissions individually across multiple repositories. To get started, customers can migrate from registry policy v1 to v2 using the ECR management console or with the new ECR put-account-setting API. New ECR accounts automatically use registry policy v2. To learn more about ECR’s registry policy and permissions, see our Amazon ECR User Guide.

🆕 Amazon ECR now supports registry policy v2 in AWS GovCloud (US), enabling IAM permission management for all ECR actions, simplifying permission control across all repositories, and improving security.

#AWS #AwsGovcloudUs #AmazonEcr

Amazon Elastic Container Registry (ECR) supports image replication between the AWS GovCloud (US) Region Amazon Elastic Container Registry (ECR) now supports the ability to replicate images in private ECR repositories across accounts and/or regions, between the AWS GovCloud (US) Regions. Storing images helps applications start up faster as image download time is reduced due to lower latency from in-region pulls. Geographically dispersed images also help you meet backup and disaster recovery requirements for your applications. Amazon ECR Replication feature provides a simple and reliable way to replicate images, and eliminates the operational burden of manually pushing images across multiple regions and accounts. With a few clicks in the Amazon ECR Console, or using the Amazon CLI, you can specify the destination account and/or region for a source repository. Once replication is turned on, ECR will automatically replicate all new images pushed in source repository to the destination region. Additionally, ECR offers granular control to replicate specific repositories. You can use repository name prefixes as filters to specify which repositories to replicate. To learn more about using replication in ECR, see our https://docs.aws.amazon.com/AmazonECR/latest/userguide/replication.html.

Amazon Elastic Container Registry (ECR) supports image replication between the AWS GovCloud (US) Region

Amazon Elastic Container Registry (ECR) now supports the ability to replicate images in private ECR repositories across accounts and/or regions, between the A...

#AWS #AwsGovcloudUs #AmazonEcr

Amazon Elastic Container Registry (ECR) supports image replication between the AWS GovCloud (US) Region Amazon Elastic Container Registry (ECR) now supports the ability to replicate images in private ECR repositories across accounts and/or regions, between the AWS GovCloud (US) Regions. Storing images helps applications start up faster as image download time is reduced due to lower latency from in-region pulls. Geographically dispersed images also help you meet backup and disaster recovery requirements for your applications. Amazon ECR Replication feature provides a simple and reliable way to replicate images, and eliminates the operational burden of manually pushing images across multiple regions and accounts. With a few clicks in the Amazon ECR Console, or using the Amazon CLI, you can specify the destination account and/or region for a source repository. Once replication is turned on, ECR will automatically replicate all new images pushed in source repository to the destination region. Additionally, ECR offers granular control to replicate specific repositories. You can use repository name prefixes as filters to specify which repositories to replicate. To learn more about using replication in ECR, see our documentation.

🆕 Amazon ECR now supports image replication between AWS GovCloud (US) regions, enabling faster startup times and meeting backup/disaster recovery needs with automatic, simple replication across accounts and regions.

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR adds support for Internet Protocol version 6 (IPv6) Amazon Elastic Container Registry (ECR) announces IPv6 support for API and Docker/OCI endpoints for both ECR and ECR Public. This makes it easier to standardize on IPv6 and remove IP address scalability limitations for your container build, deployment, and orchestration infrastructure. With today’s launch, you can pull your private or public ECR images via the AWS SDK or Docker/OCI CLI using ECR’s new dual-stack endpoints which support both IPv4 and IPv6. When you make a request to an ECR dual-stack endpoint, the endpoint resolves to an IPv4 or an IPv6 address, depending on the protocol used by your network and client. This helps you meet IPv6 compliance requirements, and modernize your applications without expensive network address translation between IPv4 and IPv6 addresses. ECR’s new dual-stack endpoints are generally available in all AWS commercial and AWS GovCloud (US) regions at no additional cost. Currently, ECR's dual-stack endpoints do not serve AWS PrivateLink traffic originating from your Amazon Virtual Private Cloud (VPC). To get started with ECR IPv6, visit https://docs.aws.amazon.com/AmazonECR/latest/userguide/ecr-requests.html or https://docs.aws.amazon.com/AmazonECR/latest/public/public-ecr-requests.html.

Amazon ECR adds support for Internet Protocol version 6 (IPv6)

Amazon Elastic Container Registry (ECR) announces IPv6 support for API and Docker/OCI endpoints for both ECR and ECR Public. This makes it easier to standardize on IPv6 and remove IP address scalabil...

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR adds support for Internet Protocol version 6 (IPv6) Amazon Elastic Container Registry (ECR) announces IPv6 support for API and Docker/OCI endpoints for both ECR and ECR Public. This makes it easier to standardize on IPv6 and remove IP address scalability limitations for your container build, deployment, and orchestration infrastructure. With today’s launch, you can pull your private or public ECR images via the AWS SDK or Docker/OCI CLI using ECR’s new dual-stack endpoints which support both IPv4 and IPv6. When you make a request to an ECR dual-stack endpoint, the endpoint resolves to an IPv4 or an IPv6 address, depending on the protocol used by your network and client. This helps you meet IPv6 compliance requirements, and modernize your applications without expensive network address translation between IPv4 and IPv6 addresses. ECR’s new dual-stack endpoints are generally available in all AWS commercial and AWS GovCloud (US) regions at no additional cost. Currently, ECR's dual-stack endpoints do not serve AWS PrivateLink traffic originating from your Amazon Virtual Private Cloud (VPC). To get started with ECR IPv6, visit ECR documentation or ECR Public documentation.

🆕 Amazon ECR now supports IPv6 for API and Docker/OCI endpoints, enabling dual-stack access for both ECR and ECR Public. This aids IPv6 standardization and removes IP scalability limits, available at no extra cost in all AWS regions.

#AWS #AwsGovcloudUs #AmazonEcr

Amazon ECR announces ECR to ECR pull through cache Amazon ECR announces ECR to ECR pull through cache, a capability that allows customers to automatically sync container images between two ECR private registries, existing across AWS regions and/or accounts. This enables customers to benefit from the reduced latency of pulling cached images in-region. With today’s release, Amazon ECR makes it easier for customers to optimize storage costs by providing a simple and reliable way to store local copies of only the images that are pulled across regions/accounts. As customers grow, they often have container deployments spread across multiple AWS regions. Storing images within the region of deployment improves application start-up times due to lower latency of in-region pulls. To achieve this, customers have to maintain copies of all images in every region, which is not cost-effective as many of these images are not deployed. ECR to ECR pull through cache allows customers to sync images between ECR registries in a cost-effective way by caching only the images that are pulled. Customers can now push images to their primary registry and configure pull through cache rules to cache images into downstream registries. On an image pull, ECR automatically fetches the image from upstream registry, and caches it into an automatically created repository in downstream registry for future pulls. Additionally, this feature supports frequent syncs with upstream, helping keep the cached images up to date. ECR to ECR Pull through cache is available in all AWS regions, excluding GovCloud (US) and China regions. To learn more, please visit our https://docs.aws.amazon.com/AmazonECR/latest/userguide/pull-through-cache.html.

Amazon ECR announces ECR to ECR pull through cache

Amazon ECR announces ECR to ECR pull through cache, a capability that allows customers to automatically sync container images between two ECR private registries, existing across AWS regions and/or accounts. This enables custom...

#AWS #AmazonEcr