Amazon ECS, a good first step on the way towards Kubernetes
November 03, 2020

Amazon ECS, a good first step on the way towards Kubernetes

Anonymous | TrustRadius Reviewer
Score 5 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Amazon Elastic Container Service (Amazon ECS)

We evaluated Amazon Elastic Container Service (Amazon ECS) for running containers in our AWS infrastructure. What we discovered was that it provided an improvement over our legacy infrastructure of classic servers. However, we also discovered that the larger development community was avoiding proprietary solutions like ECS in favor of Kubernetes. We ended up going with Amazon's EKS tool which provided us with greater reliability, flexibility and faster deploy times.
  • startup time
  • reliability
  • integration with fargate
  • documentation
  • networking
  • integration with 3rd party tools
  • scalable costs based on usage
  • fast startup times
  • distracted from ultimate solution Kubernetes
ECS is simpler than Kubernetes, but it's also much more limited a tool. It's a good fit for teams that need to perform scalable long running asynchronous tasks. Kubernetes is a tool designed to handle all your code execution needs (synchronous, asynchronous) in a repeatable way using docker, as well as providing tools for scaling, networking, and integration with third party tools. Kubernetes has a steeper learning curve, but the benefits outweigh the drawbacks in my opinion.

Do you think Amazon Elastic Container Service (Amazon ECS) delivers good value for the price?


Are you happy with Amazon Elastic Container Service (Amazon ECS)'s feature set?


Did Amazon Elastic Container Service (Amazon ECS) live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Amazon Elastic Container Service (Amazon ECS) go as expected?


Would you buy Amazon Elastic Container Service (Amazon ECS) again?


Amazon ECS is a decent tool for individuals who are already embedded in the AWS environment, who need the ability to occasionally run asynchronous tasks as docker images. It is relatively simple to setup, and doesn't require quite the knowledge or infrastructure of Kubernetes on amazon's EKS tool. However, once you're attempting to handle synchronous requests, reach more than 5 separate tasks, or have any inter task dependencies, Kubernetes and EKS come out ahead.

Amazon Elastic Container Service (Amazon ECS) Support

I cannot speak to the support for ECS directly, as during our evaluation of it, we did not have need of their services. The documentation for the tool was sufficient for starting up and running workloads on ECS. It also clearly displayed the limitations of the tool, making no mention of synchronous tasks, networking, or failover.

Using Amazon Elastic Container Service (Amazon ECS)

This is a tool that is relatively simple to start using. The hardest part of getting started is getting a docker image setup for the first time, which typically falls outside the responsibility of ECS. Getting workflows and tasks setup is simple to understand conceptually and to implement. To move beyond a simple Queue -> executor workflow is difficult and best handled by using Amazon's Elastic Kubernetes Service (EKS) instead.