Amazon Elastic Container Service (Amazon ECS)

Fault tolerance.

Availability

Scaling

Pricing is fair and reasonable.

Logging part is not so easy.

local exec into fargate container is complicated.

The UX/UI part is complicated.

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

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

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.

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.

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.

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.