I suggest making it more aligned with the Docker registry version two API specification. If they achieve this, it would be excellent. Eli is an example of such an implementation.
There were a few issues related to the roles, policies, and retrieval of data when trying to fetch images for deployment on Amazon ECS. This can involve permissions and configuration complexities.
AWS GenAI Data Engineer at a computer software company with 51-200 employees
Real User
Top 10
2024-11-08T16:18:38Z
Nov 8, 2024
The documentation could be improved, and I would say this about all AWS services. Even though AWS covers pretty much every use case there is for a particular product, the documentation for these services lacks in some way. Additionally, they could offer backwards compatibility to other containerization platforms and maybe provide legacy support.
If there were a way to use containers as tasks directly, that would simplify things. Currently, when we use EC2 instances, scaling horizontally means increasing the instance count by five times, which might not be cost-effective. Maybe using containers directly for tasks could be a better option. Setting up this product initially does take quite a bit of time, and maintaining it also requires effort. Doing it via command line would be challenging, so I find it easier to manage through the interface.
A lot of documentation is very beneficial for command-line tools like Amazon ECR. Improving the documentation for easy understanding will help bring in more clients to use Amazon ECR.
The solution provides us with image scanning. It would be great if they can also provide a reference to fix the errors or vulnerabilities in the images rather than just notifying us about them. For example, they just provide us with the issue only. But in case they provide us a way to fix the issue directly, that will be a good addition.
The solution's support for system architecture could be better. Also, there could be specific training module videos included. It is time-consuming to refer to YouTube videos to figure out the solution's architecture.
Solution Architect, DevOps Engineer at sonne technology
Real User
Top 10
2023-05-18T13:12:08Z
May 18, 2023
Amazon ECR should improve the integration with Amazon CloudWatch. For example, allowing us to monitor the queues better. Additionally, some of the features could be made more accessible.
One area for improvement in Amazon ECR is its complexity. It's pretty complex for newbies, particularly learning about private repositories, including how to access Amazon ECR through AWS Identity and Access Management (IAM). However, after your hands-on as a newbie, it becomes easy to use Amazon ECR. Amazon ECR also lacks documentation that would make learning easier for newbies. I have to teach others about IAM and its purpose, how to use it, and the access key to access private images in Amazon ECR. I want Amazon ECR to integrate with other repositories and cloud services. For example, I should be able to see the containers and images uploaded to the containers. I should see uploaded images to Docker, Azure Container Registry, etc. because that would make it easier for me to select the images for deployment. That's the feature that would be most useful for developers.
Container Registry is a service for storing, managing, and securing container images. It simplifies deploying containerized applications by ensuring consistency and control over container images.
This service supports integrating with CI/CD pipelines to automate the build, test, and deployment processes. It enhances security by scanning images for vulnerabilities and managing permissions. Users experience increased efficiency in software development cycles, from development to...
I suggest making it more aligned with the Docker registry version two API specification. If they achieve this, it would be excellent. Eli is an example of such an implementation.
There were a few issues related to the roles, policies, and retrieval of data when trying to fetch images for deployment on Amazon ECS. This can involve permissions and configuration complexities.
The documentation could be improved, and I would say this about all AWS services. Even though AWS covers pretty much every use case there is for a particular product, the documentation for these services lacks in some way. Additionally, they could offer backwards compatibility to other containerization platforms and maybe provide legacy support.
The Amazon ECR interface could benefit from improvements to enhance user experience. CloudFormation has a learning curve.
There is no room for improvement mentioned; it's good as is.
The UI for managing ECR and other services could be improved. It could be user-friendly compared to other cloud services.
Amazon ECR should include integration with Docker Hub.
If there were a way to use containers as tasks directly, that would simplify things. Currently, when we use EC2 instances, scaling horizontally means increasing the instance count by five times, which might not be cost-effective. Maybe using containers directly for tasks could be a better option. Setting up this product initially does take quite a bit of time, and maintaining it also requires effort. Doing it via command line would be challenging, so I find it easier to manage through the interface.
Amazon ECR needs to improve its downtime.
A lot of documentation is very beneficial for command-line tools like Amazon ECR. Improving the documentation for easy understanding will help bring in more clients to use Amazon ECR.
Amazon ECR's manipulation capability of tags needs to be improved.
The solution provides us with image scanning. It would be great if they can also provide a reference to fix the errors or vulnerabilities in the images rather than just notifying us about them. For example, they just provide us with the issue only. But in case they provide us a way to fix the issue directly, that will be a good addition.
The solution's support for system architecture could be better. Also, there could be specific training module videos included. It is time-consuming to refer to YouTube videos to figure out the solution's architecture.
Amazon ECR should improve the integration with Amazon CloudWatch. For example, allowing us to monitor the queues better. Additionally, some of the features could be made more accessible.
One area for improvement in Amazon ECR is its complexity. It's pretty complex for newbies, particularly learning about private repositories, including how to access Amazon ECR through AWS Identity and Access Management (IAM). However, after your hands-on as a newbie, it becomes easy to use Amazon ECR. Amazon ECR also lacks documentation that would make learning easier for newbies. I have to teach others about IAM and its purpose, how to use it, and the access key to access private images in Amazon ECR. I want Amazon ECR to integrate with other repositories and cloud services. For example, I should be able to see the containers and images uploaded to the containers. I should see uploaded images to Docker, Azure Container Registry, etc. because that would make it easier for me to select the images for deployment. That's the feature that would be most useful for developers.