Amazon EKS Reviews & Insights

We are using multiple inter dependent microservices hosted on EKS clusters. The AWS managed clusters does remove the overhead of maintanence of the master nodes and its components. The auto scaling policies and the node groups help greatly when there is a spike on the platform and does not require any manual intervention. Also it's integration with cloudwatch metrics helps a great deal to monitor the clusters and to find the root cause of the issues related to cpu, memory, pods etc.

Well suited for microservices architecture but can be a bit costly if less number of microservices or monolithic architecture hosted to be hosted on containers. Use of hybrid cluster instances also works well using both normal and fargate instances. Also the integration of audit and diagnostic logs of master nodes helps to reduce the unwanted access related issues.

We are using EKS to run all our dev and production workloads, which includes stateless and state-full applications.

It is well suited when you want to have a Kubernetes cluster in AWS Cloud and want to avoid all the management overhead of maintaining your own cluster in terms of the control plane. EKS seems to be lacking in features when compared with AKS and GKE. Backups, service mesh, and monitoring have a lot of room for improvements.