The main use case for Amazon ECR is that whatever containerized image we are building will be pushed to Amazon ECR, and then it will get deployed into a Kubernetes cluster. I appreciate that if my deployment is on Azure, I use ACR, and if my deployment is in AWS, I put all my containerized images into Amazon ECR, and then my DevOps pipeline takes that and gets deployed into the cluster.
I use Amazon ECR ( /products/amazon-ecr-reviews ) for storing Docker ( /products/docker-37146-reviews ) images. I use it to scan images for vulnerabilities automatically whenever a new image is pushed. I also maintain version control using specific tags, which helps me use the desired image tag for application deployments.
Senior Project Manager at a tech vendor with 10,001+ employees
Real User
Top 10
Jan 9, 2025
Our solution serves as an image repository for container images. We utilize two regions, including Eli Orlando, and follow a shared strategy. We maintain two large ECRs and repositories for each application. We push images into these repositories and pull images from the EKS and QM clusters.
We have been using a couple of products, but mainly AWS managed services. These include AWS API Gateway, Amazon SNS, SQS, Amazon S3, Amazon RDS, AWS Lambda, and serverless services like containers. We use Amazon ECS with Fargate and Amazon ECR for container orchestration as we have been using Docker containers.
We use ECR to host file images for our products. We are working on a few in-house products related to GenAI and agentic application. For any website or application that we're creating, we create Docker images for that.
Tech Lead - QA at a financial services firm with 10,001+ employees
Real User
Top 10
Jul 8, 2024
The solution is also used for managing containers and is integrated into our overall application hosting environment. It helps us store and manage Docker container images for our applications.
Amazon ECR is a solution for storing Docker containers and images I create. It's like an AWS version of Docker Hub, where I can store as many Docker containers as I need for any application and use these Docker images whenever I want. It also integrates with CodeDeploy. If there's a new commit or changes in the repository, the tool automatically updates the Docker images with these changes. So, I don't have to update them manually; it's all automated. I use the solution with ECS because it supports auto-scaling. I configure auto-scaling groups to scale when traffic increases horizontally. It automatically creates new tasks and instances to handle more traffic. It also scales down when traffic decreases.
We use the solution for multi-architecture and microservices applications. We must create a Dockerfile for applications and build the image using Dockerfile. After that, push this Docker image on Amazon ECR, using AWS CI/CD and building processes.
I use Amazon ECR for the containerization of different applications to be deployed. Using Amazon ECR is one of the best ways to deploy architecture, as it reduces development time and increases output. Amazon ECR is very flexible.
My current company uses monolithic and microservices architecture based on customers' wants or needs. My company's usage of Docker is now limited, and I have full permission to use Amazon ECR.
Amazon Elastic Container Registry (ECR) is a fully-managed Docker container registry that makes it easy for developers to store, manage, and deploy Docker container images. Amazon ECR is integrated with Amazon Elastic Container Service (ECS), simplifying your development to production workflow.
The main use case for Amazon ECR is that whatever containerized image we are building will be pushed to Amazon ECR, and then it will get deployed into a Kubernetes cluster. I appreciate that if my deployment is on Azure, I use ACR, and if my deployment is in AWS, I put all my containerized images into Amazon ECR, and then my DevOps pipeline takes that and gets deployed into the cluster.
I use Amazon ECR ( /products/amazon-ecr-reviews ) for storing Docker ( /products/docker-37146-reviews ) images. I use it to scan images for vulnerabilities automatically whenever a new image is pushed. I also maintain version control using specific tags, which helps me use the desired image tag for application deployments.
Our solution serves as an image repository for container images. We utilize two regions, including Eli Orlando, and follow a shared strategy. We maintain two large ECRs and repositories for each application. We push images into these repositories and pull images from the EKS and QM clusters.
We have been using a couple of products, but mainly AWS managed services. These include AWS API Gateway, Amazon SNS, SQS, Amazon S3, Amazon RDS, AWS Lambda, and serverless services like containers. We use Amazon ECS with Fargate and Amazon ECR for container orchestration as we have been using Docker containers.
We use ECR to host file images for our products. We are working on a few in-house products related to GenAI and agentic application. For any website or application that we're creating, we create Docker images for that.
I use ECR as a service that stores and manages container images. My primary use case for CloudFormation is for the automation of infrastructure.
If you are in an AWS environment and running a Kubernetes cluster, Amazon ECR is very easy to use.
The solution is also used for managing containers and is integrated into our overall application hosting environment. It helps us store and manage Docker container images for our applications.
Our complete DevOps pipeline is set up, and the images are pushed through that to Amazon ECR.
Amazon ECR is a solution for storing Docker containers and images I create. It's like an AWS version of Docker Hub, where I can store as many Docker containers as I need for any application and use these Docker images whenever I want. It also integrates with CodeDeploy. If there's a new commit or changes in the repository, the tool automatically updates the Docker images with these changes. So, I don't have to update them manually; it's all automated. I use the solution with ECS because it supports auto-scaling. I configure auto-scaling groups to scale when traffic increases horizontally. It automatically creates new tasks and instances to handle more traffic. It also scales down when traffic decreases.
We use the solution for multi-architecture and microservices applications. We must create a Dockerfile for applications and build the image using Dockerfile. After that, push this Docker image on Amazon ECR, using AWS CI/CD and building processes.
I use Amazon ECR for the containerization of different applications to be deployed. Using Amazon ECR is one of the best ways to deploy architecture, as it reduces development time and increases output. Amazon ECR is very flexible.
I'm using Amazon ECR to deploy our images on the ECS platform.
We use the solution to manage microservices.
My current company uses monolithic and microservices architecture based on customers' wants or needs. My company's usage of Docker is now limited, and I have full permission to use Amazon ECR.