We noticed a problem where our container doesn't always run, and the traffic in our secured license exceeds 100%, leading to increased container costs. We are working to understand and reduce this traffic to control costs.
There is room for improvement, particularly in logging and monitoring for the product, while integrating external third-party tools like Elastic Log Kibana and Grafana or Primatius. They could provide easier options for third-party integrations similar to internal AWS services.
Learn what your peers think about Amazon Elastic Container Service. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
Amazon EC2 Container Service should be made easier to use. Amazon EC2 Container Service should include more enterprise project management features, typically available in an OpenShift environment.
Pricing is an area of concern where improvements are required since the cloud services provided by AWS are not cheap. Due to the expensive nature of the cloud services provided by AWS, many people have opted for an on-premises deployment model. Amazon EC2 Container Service's upgradability is an area with shortcomings requiring improvements.
System Engineer at a tech services company with 201-500 employees
Real User
Top 5
2023-09-21T16:48:00Z
Sep 21, 2023
Amazon EC2 Container Service's security can be improved. For example, ECS should be integrated with multiple teams and cloud providers to make it more accessible and secure. Additionally, AWS should provide more security policies for ECS resources to prevent unauthorized access. Support could also be improved.
Billing is extremely complex. The whole concept of billing is so complicated that we never understand it. There is an upfront cost, and there is a network cost. It is impossible for me to calculate the cost, understand it, and inform the client about it. We are never sure of our end cost. Sometimes the cost blows up and ends up being five times more than what we calculated. There is no way to understand the cost. I want the solution to have a better billing system and dashboard to understand the billing. The solution could be more intuitive. If I'm using a service and my backup has gone down, there should be a notification or suggestion to help me understand what I can do. It should explain how I could have avoided the issue. EC2 is huge, and we'll never know all its services. The tool should have a way of suggesting to me what I can do better. It can be through notifications, tutorials or through their customer service team. The product could provide CI/CD services in the future.
The documentation and usage for the users can be better because for new users it can be very hard to understand and use the solution. They can add small images and accessories.
Service Delivery Manager / Architect at a tech services company with 201-500 employees
Real User
2021-05-04T11:15:26Z
May 4, 2021
We faced challenges with AWS and I feel the support could have been better - more timely with their response, more knowledgeable staff and more customer friendly. As a partner, I'd like to see a response from the appropriate team and know that they'd help us throughout. AWS is in partnership with other product vendors in developing the connectors and could have given a direction to another vendor, Tableau, for example, because when we try to use those connectors to hook up the data into cloud, it was challenging and a very difficult exercise to go through with AWS in order to resolve the problem. Both sides tell us it's not their problem.
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.
We noticed a problem where our container doesn't always run, and the traffic in our secured license exceeds 100%, leading to increased container costs. We are working to understand and reduce this traffic to control costs.
The solution must improve backup and compatibility around OS like Windows and Mac.
There is room for improvement, particularly in logging and monitoring for the product, while integrating external third-party tools like Elastic Log Kibana and Grafana or Primatius. They could provide easier options for third-party integrations similar to internal AWS services.
I would like the product to improve integration with different platforms.
Amazon EC2 Container Service needs to improve the menu design. It needs to improve deployment with better documentation.
The product can become expensive if you don't choose what you want.
The product should improve its price.
There is room for improvement in the licensing costs. There can be better licensing costs.
Amazon EC2 Container Service should be made easier to use. Amazon EC2 Container Service should include more enterprise project management features, typically available in an OpenShift environment.
Pricing is an area of concern where improvements are required since the cloud services provided by AWS are not cheap. Due to the expensive nature of the cloud services provided by AWS, many people have opted for an on-premises deployment model. Amazon EC2 Container Service's upgradability is an area with shortcomings requiring improvements.
Amazon EC2 Container Service's security can be improved. For example, ECS should be integrated with multiple teams and cloud providers to make it more accessible and secure. Additionally, AWS should provide more security policies for ECS resources to prevent unauthorized access. Support could also be improved.
I would like fewer updates.
The solution needs to improve backup and pricing.
Billing is extremely complex. The whole concept of billing is so complicated that we never understand it. There is an upfront cost, and there is a network cost. It is impossible for me to calculate the cost, understand it, and inform the client about it. We are never sure of our end cost. Sometimes the cost blows up and ends up being five times more than what we calculated. There is no way to understand the cost. I want the solution to have a better billing system and dashboard to understand the billing. The solution could be more intuitive. If I'm using a service and my backup has gone down, there should be a notification or suggestion to help me understand what I can do. It should explain how I could have avoided the issue. EC2 is huge, and we'll never know all its services. The tool should have a way of suggesting to me what I can do better. It can be through notifications, tutorials or through their customer service team. The product could provide CI/CD services in the future.
There is room for improvement in the pricing of Amazon EC2 Container Service. Also, mainly on the network issues to access the container.
The documentation and usage for the users can be better because for new users it can be very hard to understand and use the solution. They can add small images and accessories.
The solution can still be expensive, even with per-second billing.
There is nothing I would like to change about the solution at this time. The pricing could be a bit better. The Amazon Cloud expense can get high.
We faced challenges with AWS and I feel the support could have been better - more timely with their response, more knowledgeable staff and more customer friendly. As a partner, I'd like to see a response from the appropriate team and know that they'd help us throughout. AWS is in partnership with other product vendors in developing the connectors and could have given a direction to another vendor, Tableau, for example, because when we try to use those connectors to hook up the data into cloud, it was challenging and a very difficult exercise to go through with AWS in order to resolve the problem. Both sides tell us it's not their problem.