The more containers there are, the more expensive the solution becomes. With Amazon Elastic Container Service, we lack full control over the infrastructure. Since it is a managed service for container orchestration, it may limit our control over certain infrastructure functions. This limitation can be a concern if you require deep control over your container or have specific infrastructure requirements.
There don't seem to be any improvements needed for ECS at the moment. I will consider them once I get my projects running smoothly and understand the costs better.
Learn what your peers think about Amazon Elastic Container Service. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
The solution could provide more reliability. There could be an option for the customers to manage the services. Also, there need to be more custom features that would allow customers to access the ECS containers and deploy them.
I see they have changed the console a bit to make it easier to use. Probably, they should include automated graphing, and monitoring solutions. Currently, I have to set up all of those by myself.
Visualization is an important factor for me, and I don't think that the visuals within ECS are good enough because it doesn't show you all the details you might need to see at a glance. Another aspect that could be improved is that our monitoring within ECS depends on other services like CloudWatch, for example, and with this arrangement you have to constantly switch between screens when navigating around. Because of this, it's difficult to take a look at your monitoring data, or even just to set up, and it can be very frustrating. Perhaps it would be possible to improve this situation by having the ability to include everything on one status page. For example, if there is a service or container that is exhibiting a bug or is in some type of loopback mode, when I click on it, I could be shown the screen with all the errors displayed right there.
Deputy CTO at a tech company with 51-200 employees
Real User
2021-06-25T17:54:45Z
Jun 25, 2021
This is a really good tool, but it's complex because you need to understand how it works to get the best of this tool. It would help if things were simplified so it could be more user friendly.
The problem with containerization technology is that many businesses do not trust it right now, and only use it in their development environment. For example, if you spin down the container then all of the data inside it gets deleted. From our perspective, we think that this technology is good, and it is really an issue of awareness. I am very much excited by this technology and am okay with it. I think that it would help if the vendor provided more use cases and explanations as to how ECS can be utilized.
DevOps Engineer at a financial services firm with 10,001+ employees
Real User
2020-08-23T08:17:29Z
Aug 23, 2020
Sometimes, the instances fail under the ECS container cluster, and we have to manually go and find out the black sheep in the ECS container instance. We had an issue earlier where one of the instances under the ECS container cluster went down, and we were not able to identify that instance. The instance got terminated, but a new instance did not come up. Therefore, I had to manually get that instance up. It could be optimized better. In production, we normally cannot sustain such things. It can be optimized in terms of instances, durability, and serving the requests of customers.
Amazon Elastic Container Service (Amazon ECS) is a highly scalable, high-performance container orchestration service that supports Docker containers and allows you to easily run and scale containerized applications on AWS. Amazon ECS eliminates the need for you to install and operate your own container orchestration software, manage and scale a cluster of virtual machines, or schedule containers on those virtual machines.
The solution must improve backup and compatibility around OS like Windows and Mac.
The more containers there are, the more expensive the solution becomes. With Amazon Elastic Container Service, we lack full control over the infrastructure. Since it is a managed service for container orchestration, it may limit our control over certain infrastructure functions. This limitation can be a concern if you require deep control over your container or have specific infrastructure requirements.
The solution's pricing could be improved. With Amazon Elastic Container Service, you spend a lot of money in the long term.
There don't seem to be any improvements needed for ECS at the moment. I will consider them once I get my projects running smoothly and understand the costs better.
Amazon Elastic Container Service’s initial setup is a bit difficult. You need to have experience in order to set it up.
The orchestration of the workloads running in ECS needs improvement. Additionally, they should automate the auto-scaling features for containers.
The solution could provide more reliability. There could be an option for the customers to manage the services. Also, there need to be more custom features that would allow customers to access the ECS containers and deploy them.
The solution is expensive compared to other alternatives like Azure.
I see they have changed the console a bit to make it easier to use. Probably, they should include automated graphing, and monitoring solutions. Currently, I have to set up all of those by myself.
Visualization is an important factor for me, and I don't think that the visuals within ECS are good enough because it doesn't show you all the details you might need to see at a glance. Another aspect that could be improved is that our monitoring within ECS depends on other services like CloudWatch, for example, and with this arrangement you have to constantly switch between screens when navigating around. Because of this, it's difficult to take a look at your monitoring data, or even just to set up, and it can be very frustrating. Perhaps it would be possible to improve this situation by having the ability to include everything on one status page. For example, if there is a service or container that is exhibiting a bug or is in some type of loopback mode, when I click on it, I could be shown the screen with all the errors displayed right there.
In the next release, they could add some customization options for high computer workloads.
This is a really good tool, but it's complex because you need to understand how it works to get the best of this tool. It would help if things were simplified so it could be more user friendly.
The problem with containerization technology is that many businesses do not trust it right now, and only use it in their development environment. For example, if you spin down the container then all of the data inside it gets deleted. From our perspective, we think that this technology is good, and it is really an issue of awareness. I am very much excited by this technology and am okay with it. I think that it would help if the vendor provided more use cases and explanations as to how ECS can be utilized.
Sometimes, the instances fail under the ECS container cluster, and we have to manually go and find out the black sheep in the ECS container instance. We had an issue earlier where one of the instances under the ECS container cluster went down, and we were not able to identify that instance. The instance got terminated, but a new instance did not come up. Therefore, I had to manually get that instance up. It could be optimized better. In production, we normally cannot sustain such things. It can be optimized in terms of instances, durability, and serving the requests of customers.