Amazon Elastic Container Service (Amazon ECS)

Amazon Elastic Container Service (Amazon ECS)

About TrustRadius Scoring
Score 8.4 out of 100
Amazon Elastic Container Service (Amazon ECS)


Recent Reviews

Reviewer Pros & Cons

View all pros & cons

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Amazon Elastic Container Service (Amazon ECS), and make your voice heard!


View all pricing

AWS Fargate Launch Type Model

Spot price: $0.0013335. Ephemeral Storage Pricing: $0.000111

per hour per storage

Amazon EC2 Launch Type Model



Amazon ECS on AWS Outposts



Entry-level set up fee?

  • No setup fee


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Starting price (does not include set up fee)

  • $0 per hour per GB

Features Scorecard

No scorecards have been submitted for this product yet..

Product Details

What is Amazon Elastic Container Service (Amazon ECS)?

Amazon Elastic Container Service (Amazon ECS) is a scalable, high performance container management service that supports Docker containers.

Amazon Elastic Container Service (Amazon ECS) Video

A Quick Introduction to Amazon ECS by Amazon Web Services.

Amazon Elastic Container Service (Amazon ECS) Technical Details

Deployment TypesSaaS
Operating SystemsUnspecified
Mobile ApplicationNo


View all alternatives

Frequently Asked Questions

What is Amazon Elastic Container Service (Amazon ECS)?

Amazon Elastic Container Service (Amazon ECS) is a scalable, high performance container management service that supports Docker containers.

How much does Amazon Elastic Container Service (Amazon ECS) cost?

Amazon Elastic Container Service (Amazon ECS) starts at $0.0013335.

What is Amazon Elastic Container Service (Amazon ECS)'s best feature?

Reviewers rate Support Rating highest, with a score of 8.6.

Who uses Amazon Elastic Container Service (Amazon ECS)?

The most common users of Amazon Elastic Container Service (Amazon ECS) are from Enterprises (1,001+ employees) and the Information Technology & Services industry.

Reviews and Ratings




(1-6 of 6)
Companies can't remove reviews or game the system. Here's why
Scott Kennedy | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
At my company we build lots of internal applications for various functions such as operations (warehouse management things), marketing, customer service etc. Each of these applications supporting their respective function(s) has a variable amount of users that may need to use the application at any given time. With ECS, we are able to scale our availability based on the amount of users fluidly.
  • Flexibility in pricing
  • Ability down grade the usage when user count is low
  • Ability to scale to a large user base quickly
  • A cleaner container service road map
  • It would be. nice to have more AI recommended cluster reductions
  • The UX could use some simplification
The ability to customize how your product works plays a big role in the decision process. Whether you need help on the processor, storage, or networking side, choosing the right style of ECS is important. We are using ECS mainly on the storage side, which is well suited if one of our applications ends up needing to load a ton of data.
Abdullah Khawer | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
We are using Amazon ECS to run our application services as Docker containers in the clusters in various environments. It is being used by the whole organization. Some of our stuff is running on Amazon EKS as well. We are mainly using Amazon ECS to run our application. Amazon ECS gives us an environment that is mostly managed by AWS to ease our job.
  • AWS Managed
  • Serverless using Fargate
  • High Availability
  • Better integration with other AWS services
  • Load Balancing using AWS Elastic Load Balancer
  • Storage Autoscaling
  • Auto Multi-region Deployment in case of unavailability of the region
  • Logs Searching and Filtering
Amazon Elastic Container Service (Amazon ECS) is well suited where you need the ease of managing the clusters by letting AWS do the stuff for you. Obviously, whenever you want to run the docker based workloads, it is always better to go for either AWS ECS or AWS EKS. If you are interested in staying at AWS only and don't want to be cloud-agnostic, then go for AWS ECS instead of AWS EKS. AWS ECS is cheaper than AWS EKS and also more managed by AWS and better integrated with other AWS services. If you want to run those workloads as serverless, then AWS ECS Fargate is the best option to go with. If you already have a Kubernetes based setup that you want to migrate to AWS, then go for AWS EKS instead of AWS ECS.
Score 10 out of 10
Vetted Review
Verified User
Review Source
We are currently using Elastic Containers as the base for some of our services, as well as for other companies to deploy the software we maintain and develop for them. Mainly it helps to build solutions that are more reliable, with little complexity and helps leverage the experience in the market related to containers (Dockers).
  • Easy to deploy.
  • Reliability.
  • Good integration capabilities.
  • Simple configuration.
  • There is room for better documentation.
  • Is not exactly Kubernetes (there is more knowledge in the market on this orchestrator).
  • Logging can be difficult.
If you are already on Amazon Web Service, Elastic Containers is our platform of choice because of the knowledge we have about it and the flexibility it offers, being many times easier to use than Kubernetes. It integrates without problems with most Docker containers we use and it is very simple to run any container. Most of the times you can use AWS web console without touching the CLI.
Support is relatively good, although the documentation sometimes is lacking, as well as outdated in our experience, especially when we initiated the process of using this service. But once we found how to assemble things, we haven't really required support from anyone at AWS, the service works without problems so we haven't had the need to contact support, which speaks well of how ECS is built.
Apurv Doshi | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We use Amazon ECS to host our multiple web solutions on a single EC2 machine. These solutions require different components, environments, and software to run smoothly. However, they might have a conflict with each other. One way is to host them on separate machines and another way is to use Amazon ECS which provides container service to create a separate environment for each solution. We use Amazon ECS to solve this problem effectively and we use it across the organization.
  • One of the biggest advantages is the flexibility to change underlying EC2 instances. As the traffic or demand increases, we can easily change EC2 instances without any issues.
  • Amazon ECS APIs are extremely robust and one can start and stop containers by firing one post request only. So, it is not mandatory to keep the demo solutions up for every time. Just at the time of demo fire the command - make the container up and running - do the demo - down the container with API. A simple portal can control every container which helps non-technical (sales, marketing) to do the demo without keeping the solutions up for the entire time frame.
  • The integration between ECR and ECS is bit tricky. It takes little extra learning curve to integrate seamlessly.
  • To set up the right configuration using cloudformation is also difficult. This flexibility of configuration costs extra complexity.
If you want to host multiple solutions with the different needs of setup and configurations, container service is really useful. It can be plugged easily with CI cycle. That helps to keep the container up to date without affecting other containers hosted on the same machine.
If the need is to host one or two solutions only, this service is not going to help, as to setup individual solutions on stand-alone machines is quite easy compared to container services.
Amazon ECS has really good documentation across the entire service. The AWS community is also quite active on the issues you post while setting ECS. Also being a partner of Amazon, we receive excellent support from their end as well.
Score 10 out of 10
Vetted Review
Verified User
Review Source
Amazon ECS is being used company-wide and is being used in many different capacities. We utilize our AWS environment for both production services as well as for testing and research capabilities. ECS is being used across instances using Fargate or just as a mechanism with generic ec2 instances.
  • Well Integrated - As with the majority of AWS services, ECS works will with any other AWS product (Route 53, CloudWatch, IAM, etc).
  • Easy to get started with - It is easy to get started building just about anything in AWS and using ECS is no exception to this rule. Be careful though -- AWS lets you do/build anything in any way you could think of and allowing yourself to shoot yourself in the foot is no exception.
  • Another AWS Service - While AWS has a service for just about everything, that is also a negative point. There is no service that does 4 out of 4 things you need. This service does 3 out of 4, another service does the fourth thing you need and another two things that the other service does.
  • With AWS things in general, it's really hard to remain cloud agnostic. Keep that in mind.
If you are containerizing your applications and using AWS, you are more than likely using or should be using ECS. It's a great service and if you aren't using Kubernetes, it's definitely worth giving it a shot.
AWS support is usually pretty good at solving issues and pretty quick with communication, but buyer beware - this is a market where what you are paying matters. The higher the support tier, as with anything else, the better service you receive.
Marcelo Araujo | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
The Amazon ECS is used by all the people from the development team here. The structure helps us a lot. In Amazon ECS we can run all of our backend projects and some tests. It is not so simple to configure but when you do it, it becomes a very easy tool to work. Amazon offers other features that are very important to us, like Amazon RDS.
  • Scalable.
  • It provides us the possibility to run all of our back-end projects.
  • Other Amazon features help us a lot.
  • It could give us more time to test.
  • It is not simple to configure.
  • Some information is confusing.
Amazon ECS is recommended when you are looking for a very good server container to work with. It is the first name when you think about the cloud. And it has built for big projects. As I said, it could be a little bit easier to configure. Some information is confused sometimes.
My experience with Amazon's support is very good. It is easy to find Amazon content on the internet. Amazon services are so famous and almost everyone uses it for running their projects. It helps us a lot to find support too. So support is not a problem to us.