Amazon Elastic Kubernetes Service (Amazon EKS) Reviews & Product Details

Smoothly integrtes with ECS and other AWS services like RDS. It is easy to setup and scale. Helps to ease deployments to Kubernetes Clusters. For small teams it saves the DevOps effort for management of kubernetes infrastructure. Review collected by and hosted on G2.com.

AWS EKS along with myriad of AWS services can be overwhelming for beginners. Scaling costs are significant so if your scale is low, the cost may be unjustified.

EKS also has steep learning curve due to internal networking ,ingresses and secret management involved. Review collected by and hosted on G2.com.

AWS K8s Service is a top-notch service to manage your Kubernetes workloads on AWS clouds. The services are based on bare-bones K8s services but integrated into AWS systems and make it easier to set up and deploy. Review collected by and hosted on G2.com.

Like any Kubernetes service, EKS is complex to learn and administer, and has a steep learning curve. It is also quite costly for smaller workloads as the control-plain has its dedicated pricing. Review collected by and hosted on G2.com.

Things such as fargate and managed nodegroups compliment the EKS pretty well. Took me less then 2 weeks to finish an all rounded POC using terraform for the entire setup. Would reccomend. Review collected by and hosted on G2.com.

With its configurability comes complexity. You would have to learn a bunch of tools such as karpenter to even have the basics of a production grade cluster. Review collected by and hosted on G2.com.

The AWS managed node group is the best park of EKS service. Never imagined it ll be so easy to administer the kubernetes cluster. Review collected by and hosted on G2.com.

AWS Managed clusters sometimes enforces an intermittent service degradation. Ideally it should be 0 downtime upgrade but that doesn't happen always. Review collected by and hosted on G2.com.

The fact that Amazon EKS is a fully managed service is one of the aspects of it that I like the most. As a result, I can stop worrying about the supporting infrastructure, including the worker nodes and control plane nodes for Kubernetes. All of that is handled for me by Amazon EKS.

I also appreciate how seamlessly Amazon EKS interfaces with other AWS services. For instance, I can use Amazon Auto Scaling to scale my Kubernetes automatically clusters up or down in response to demand and use Amazon CloudWatch to monitor my clusters.

The advantages are that it is a fully-managed service , integrates well with other AWS services, easy to use and scalable. Review collected by and hosted on G2.com.

A little bit expensive. Not as flexible as self-managed Kubernetes Review collected by and hosted on G2.com.

It is well suited once you need to have a Kubernetes cluster in AWS Cloud and need to maintain a strategic distance from all the administration overhead of keeping up your claim cluster in terms of the control plane. It's simple to coordinate other k8s tooling with EKS like a lens(IDE for k8s) etc. It is exceptionally simple to convey to a distant degree it moreover decreases the time to convey as compared to the manual arrangement. Review collected by and hosted on G2.com.

Not a dislike, but I believe AWS IAM integration with Kubernetes RBAC could get better.

Empowering a few add-ons like service mesh, and observing will be decent rather than having to introduce them yourself after the creation of the cluster.

EKS bootstrap time may well be speedier in upcoming time. Review collected by and hosted on G2.com.

Being the regular user of Amazon eks what I like the most about eks is it is fully managed, having master slave architecture master is fully managed by aws team, you just need to take care of your own slave nodes.

This enables the user to focus on actual problem and eks deployments instead of managing the eks only. Review collected by and hosted on G2.com.

Production infrastructure needs to be highly available and stable when eks used in production infrastructure it needs to be stable, there are some instance where eks goes down and I turn affects the pods running in them.

Example being :- If vpc cni goes in degrade state it affects the whole eks cluster this should be managed by eks team with zero down time. Review collected by and hosted on G2.com.

It offers free tier for one year then you can choose pay per use model and the cost associated with AWS services are less when compared to other service providers s.

It has rich documentation which you can refer and work with the resources and the scalability and elasticity features of AWS are best as you can scale your application as per needs. Review collected by and hosted on G2.com.

I don't have any dislikes with AWS services and I think it's one of the best service provider when compared to Azure and GCP and offers wide range of services to work. Review collected by and hosted on G2.com.

Access to a lot of services which fulfill the requirments for different apps. Also with managed services, it is easier to focus on the application part rather then get bogged down by infrstructue reated details. Review collected by and hosted on G2.com.

Some of the services are not available in every region and we are sometimes restricted where can deploy the service.Similarly the limits and the expected performance of the availble services vary from region to region. Review collected by and hosted on G2.com.

The ease of use and less complexity. Automation around EKS and the supporting tools makes it go-to solution. Review collected by and hosted on G2.com.

Nodegroup management and the ability to bin pack the workloads. Review collected by and hosted on G2.com.