Amazon Elastic Container Service (Amazon ECS) Reviews and Ratings

Use Cases and Deployment Scope

We use Amazon Elastic Container Service (Amazon ECS) to deploy containerised versions of the microservices which make up our systems. Amazon Elastic Container Service (Amazon ECS) allows us to easily deploy and scale microservices as needed without the hassle of managing multiple tiers of server architecture. Amazon Elastic Container Service (Amazon ECS) also provides as container registry service which gives us a storage facility for our private container images.

Likelihood to Recommend

Amazon Elastic Container Service (Amazon ECS) is well-suited for deploying containerised applications within AWS environments, especially when tight integration with other AWS services like IAM, CloudWatch, S3 and ALB is required. It’s ideal for systems which require simplicity with managed orchestration or serverless compute via Fargate. However, it’s less appropriate for multi-cloud or hybrid workloads due to limited portability, or for systems needing advanced orchestration features like those offered by Kubernetes for complex, large-scale deployments.

Use Cases and Deployment Scope

Container based microservice solution

Likelihood to Recommend

Is one of the option to use search-as-service, especially suitable, if the AWS is used as the application plattform

Use Cases and Deployment Scope

We use Amazon Elastic Container Service(ECS) for deploying our production services. So, it is the backbone of our infrastructure. All the microservices are deployed on ECS in EC2 instances.

For any SaaS application like ours, we need to deploy it on cloud and that's where ECS comes into picture.

ECS is special in the sense that it takes care of the orchestration and we only need to specify the instance size, number of instances and other configurations to connect with other services like RDS for database and Secret Manager for credentials etc. and it takes care of the deployment.

Likelihood to Recommend

Amazon ECS is well suited for the scenarios where you want to deploy a microservice to a cloud and instead of manually specifying instance size, number of instances and then specifying the configurations and connecting it with other cloud services like database service, secret manager service etc., you just want to specify these configurations as a file and using that file, the ECS would deploy the service and keep it healthy.

It might be less suited for a scenario when you don't want to stick to AWS specific solution for your microservice deployment.

The ECS configuration file is specific to AWS ECS and may not be useful for other cloud providers like Azure etc.

Use Cases and Deployment Scope

We run all of our production hosts on Amazon Elastic Container Service (Amazon ECS) for multiple services. It allows us to quickly deploy and scale up/down services without spending time and costs on infrastructure

Likelihood to Recommend

Amazon Elastic Container Service (Amazon ECS) is worth putting work in to adapting your deployment and infrastructure. We use Fargate services and our deployment pipeline is very smooth. We can update and scale up/down within minutes, and have great visibility into container performance.

Use Cases and Deployment Scope

If you want to operate your containerized services on AWS, then the simplest way is to use ECS, especially with Fargate instances. Imagine having just to specify what docker image you need to run in a task definition, then you can already launch a new ECS service with that image, with all the health checks, load balancing, and pod management done automatically.

Likelihood to Recommend

So you have containerized your app, & want to deploy it to AWS now. Then, the simplest way is to use ECS. Using Fargate instances, you don't have to be concerned with setting up an EC2 cluster to deploy the containers. However, if you're more familiar with a full Kubernetes setup, & are ready to deal with the accompanying complexity, then EKS could be a better choice, as obviously, you have more control over the whole setup with EKS compared to ECS.

Use Cases and Deployment Scope

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 highly available and reliable where we run our production workloads.

Likelihood to Recommend

To begin with it's still not kubernetes. Kubernetes has more native support and easily integrated with a lot of tools. With ECS you're more tied to what AWS provides regarding logging monitoring. ECS can be used as solution if you're trying to run simple workloads where you dont need a lot of computation power. You can have a good implementation to save some money. If you're using Fargate, you will be billed to what vCPU and memory your application is requesting.Again, it depends on your use case and what do you want to achieve.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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).

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.