Amazon Elastic Container Service (Amazon ECS)

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.

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.

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.

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.

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.

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.

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.