Amazon Elastic Container Service (Amazon ECS) vs. Red Hat Advanced Cluster Management for Kubernetes

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.

Incentivized

Well suited for - Large-scale Edge deployments of OpenShift instances. Policy-based consistency for all workloads is Less appropriate for - Small-scale deployments. Stand-alone deployments of K8s clusters. Deployments in the same data center.

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

Incentivized

• Continuous deployment of other OpenShift instances.
• Controls clusters and applications from a single console.
• Built-in Security & compliance.

• A cleaner container service road map
• It would be. nice to have more AI recommended cluster reductions
• The UX could use some simplification

Incentivized

• Initial deployment of the ACM itself needs to be made easy.
• Dependency on the Software versions of underlying open shift workloads during upgrades.
• LCM of ACM itself.

Support is relatively good, although the documentation sometimes is lacking, as well as outdated in our experience, especially when we initiated the process of using this service. But once we found how to assemble things, we haven't really required support from anyone at AWS, the service works without problems so we haven't had the need to contact support, which speaks well of how ECS is built.

Incentivized

EKS is a Kubernetes technology and you need to learn Kubernetes and build a cluster before using it. So there's a learning curve here. ECS was easier to implement and simpler to have in our use case. It takes less time to run a workload and make it available.

I have also used TNA by Google Cloud, but that is not mature enough as ACM. Right now, ACM is the best choice as a cluster manager for private cloud data centers.

• We achieved minimum downtime.
• The autoscaling kept the performance of the services great.
• We saved money by running the workloads on AWS ECS in Fargate mode by having different settings for different services to save on the hardware configuration side as well as having scheduled tasks.

Incentivized

• Reduced the deployment duration of individual nodes by 50%.
• Acts as a central manager for all the clusters.
• Provides a lot of infrastructure options (storage, networking, etc) to build instances of your choice.