Amazon Elastic Container Service (Amazon ECS) vs. Azure Kubernetes Service (AKS)

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

At one instance, there was a fire in our data center and the backup power had some issues because of which the whole DC went down. I believe with AKS and the replication it's easier to handle such a situation. Also, the scenario would have been pretty transparent to the end-users.

Incentivized

• 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

• Highly repeatable process
• Minimizes the amount of software to install
• Easily scale resources to meet demand

Incentivized

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

Incentivized

• Need to update cluster manually
• Policies cannot be updated for existing components
• if any change in policy every has to create cluster

Incentivized

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

Microsoft support was really good, whenever we raise any ticket they come back to us within a couple of hours.

Incentivized

If you are using AWS, you will be using Amazon ECS. I have also used Azure Container Instances and it works just as well in Azure as ECS does in AWS. It's really all a matter of what cloud provider you are utilizing. Because of the "Cloud Wars," it's difficult to measure cross-cloud connectivity, but I have had better luck remaining cloud agnostic in other cloud providers than AWS (Azure, GCP). Because of the sheer volume of tooling in AWS and inter-connectivity between them, it's almost easier to be fully AWS if you are using it in any kind of capacity.

Incentivized

The ability to create new instances (i.e. elastic provisioning) is probably the fastest with Azure Kubernetes Service compared to the alternatives that I have looked at. From a pricing perspective, Microsoft always seems to find a way to be more competitive in this area, and literally every other field they play in.

Incentivized

• 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

• Positive impact in moving applications to cloud from the in-hose data center to save cost
• Sometimes got affected with some bugs on the AKS infrastructure but hasn't caused a big kios as our production footprint in AKS is not yet high

Incentivized