G2 Vendor Directory

Amazon Elastic Container Registry (ECR)

by Amazon Web Services (AWS)

118

Reviews

4.3

Star rating

#3

Rank in Container Registry

Pros and cons

Pros

    Cons

      Traffic & LLM citations

      Monthly G2.com page views and citations by AI answer engines for Amazon Elastic Container Registry (ECR).

      Page views and citations · Amazon Elastic Container Registry (ECR)

      Source: G2 review data

      Winning from

      Based on reviewers who said they switched from another product.

      Losing to

      Based on reviewers of other products who said they switched from Amazon Elastic Container Registry (ECR).

      Key stats

      +0.0%

      55

      Mid-Market

      1

      Adoption by company size

      SegmentShare of reviews
      Small Business22.9%
      Mid-Market44.9%
      Enterprise32.2%

      Quarterly history

      QuarterReviewsStar rating
      2025 Q214.5
      2025 Q414.5
      2026 Q214.5
      2026 Q314.5

      Satisfaction ratings

      Ease of Use8.9
      Ease of Setup9.1
      Quality of Support8.9
      Meets Requirements9.0

      What reviewers say

      Detailed Review - Elastic Container Registry

      4.5

      “What I like best about ECR is its ability) to integrate with other AWS services, like ECS, EKS, and Lambda, which makes containerized application workflows smooth. It also provides scalable storage for container images without having to manage the infrastructure.”

      Visiting Scholar

      ECR makes it easy to deploy containers to other AWS services

      4.0

      “ECR makes it easy to deploy containers to other AWS services such as Lambda and ECS. It is easy to use and the cost is acceptable.”

      Senior Fullstack Developer

      Your private image repository

      4.5

      “It is very easy to configure and use. Any image can be quickly downloaded or uploaded to the repository with any tag. Our use case for the ECR is to keep the docker images from our applications that are then deployed to AWS Elastic Beanstalk.”

      Principal Backend Developer