My personal experience with ECS.
We use ECS to run our containerised applications and on fargate instances so we don't need to worry about managing EC2 instances. It's …
Starting at $0 per hour per GB
View PricingOverview
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.
Recent Reviews
Reviewer Pros & Cons
Pricing
AWS Fargate Launch Type Model
Spot price: $0.0013335. Ephemeral Storage Pricing: $0.000111
Cloud
per hour per storage
Amazon EC2 Launch Type Model
Free
Cloud
Amazon ECS on AWS Outposts
Free
Cloud
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $0 per hour per GB
Product Details
- About
- Tech Details
- FAQs
What is Amazon Elastic Container Service (Amazon ECS)?
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 Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
Amazon Elastic Container Service (Amazon ECS) is a scalable, high performance container management service that supports Docker containers.
Amazon Elastic Container Service (Amazon ECS) starts at $0.0013335.
Reviewers rate Support Rating highest, with a score of 8.4.
The most common users of Amazon Elastic Container Service (Amazon ECS) are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(42)Attribute Ratings
Reviews
(1-4 of 4)Companies can't remove reviews or game the system. Here's why
May 11, 2020
Elastic Container Service from AWS a no brainer
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.
- It decreases the cost of deploying solutions compared to building our own EC2 clusters.
- Downtime due to upgrades on our applications was almost eliminated.
- Cost of integration with other services is smaller.
We like Elastic Containers better because of the simplicity to create an application without losing control over it. It is simple, yet powerful, exposing only the parts that are needed without complicating the access to the nuts and bolts when more complicated adjustments are required. Especially when private/public networking and load balancing is required.
January 29, 2020
Amazon ECS - An elegant way to containerize your solutions
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.
- We run 8 web applications (demo instances) on a single machine. At a particular time, no more than 3 applications run simultaneously. So, we keep only required containers up. This helps us to provision small EC2 machines without compromising performance.
- Overall Amazon ECS helps to have less number of dedicated machines as more than one solution can be deployed on a single instance. This reduces costs a lot.
December 07, 2019
If you are using containers and AWS, you're likely already using it!
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.
- Azure Container Instances
If you are using AWS, you will be using Amazon ECS. I have also used Azure Container Instances and it works just as well in Azure as ECS does in AWS. It's really all a matter of what cloud provider you are utilizing. Because of the "Cloud Wars," it's difficult to measure cross-cloud connectivity, but I have had better luck remaining cloud agnostic in other cloud providers than AWS (Azure, GCP). Because of the sheer volume of tooling in AWS and inter-connectivity between them, it's almost easier to be fully AWS if you are using it in any kind of capacity.
November 20, 2019
Amazon ECS is the best option for your projects
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.
- Allow us to run many projects at the same time.
- 1-year free for testing.
- Security of Amazon services.