Amazon EKS Reviews

For the usual use cases of Amazon EKS, we have been running different kinds of servers, such as web pages, and we have also used it to provide the SaaS solution for the end customer, delivering software as a service to the end customers. Basically, I deal with apps, SaaS applications, and websites.

We don't use Amazon EKS internally for us; we usually provide the service to others for their solutions.

The most valuable capability of Amazon EKS is managing the management portion of Kubernetes, which is the best thing that we get from Amazon EKS. Even though we have to upgrade it every six to seven months, it provides all the things required for us, so if a person knows how to install it and make use of it, that's all that's needed for using Amazon EKS.

Regarding self-healing nodes of EKS in minimizing administrative burdens for my customers, I appreciate that this feature allows nodes to try to heal themselves, which is a good feature. However, I haven't used this feature often, but having the service's ability to find and heal themselves or replicate is a good option for Amazon EKS to maintain high infrastructure uptime.

The area of Amazon EKS that could be improved is the development cycles because every six months a new version of Kubernetes is launched. Working in the infrastructure, I have found it quite difficult to keep up with infrastructure updates and new versions. Migrating the whole infrastructure from one Amazon EKS cluster to another is quite cumbersome, so if possible, version management should be made much easier than it is now, perhaps with some option to deploy code using blue-green updates. Creating a clone of the current infrastructure, updating it to the latest version, and terminating the old infrastructure would be a great enhancement.

I haven't used Amazon EKS's automated patching feature, but I believe it involves directly upgrading the AMI versions remotely or from the Amazon EKS dashboard. I understand it is a good feature, but I haven't used it yet.

I have been working with Amazon EKS for seven years in Kubernetes only, and I would say four years in Amazon EKS specifically.

My experience with the deployment and initial setup of Amazon EKS is usually straightforward. If you have the right Terraform code or the right knowledge, you can create it from the console or using Terraform or other tools; I don't find difficulties in starting a Kubernetes cluster. However, using the right principles or tools together with Amazon EKS may be challenging.

In terms of stability, Amazon EKS is pretty good. I don't encounter issues with stability if I use the right methods of deployment. For instance, using spot instances that are inexpensive can lead to downtime if not managed correctly.

My experience with customer service and technical support of AWS for Amazon EKS has been generally positive. Earlier, I was in developer support where the response time was maybe three to four hours after ticket submission, but I was able to resolve most problems with their support. I don't have any complaints.

I would rate technical support for Amazon EKS at an eight out of ten based on my experience with the developer support.

I have been using Amazon EKS for four years. In addition, I have used other solutions.

The integration of Amazon EKS with IAM is easy; if you have the right policy in place, you can create a role from the policy and then apply it to the application that you are using. It provides a way to use IAM to provision the software and infrastructure portions, as well as integrating application users into AWS IAM, making it very easy to implement if you know how to do it.

The influence of EKS's integration with other AWS tools on application development and management processes is significant; EKS itself is just the infrastructure. Application development requires the right tools with Amazon EKS, as it only provides a place to deploy things, and not the entire development cycle or management of workstations and servers. You must use something on top of Amazon EKS to fulfill the development cycle or CI/CD pipeline. Once the CI/CD pipeline is developed with Amazon EKS as the deployment platform, it becomes easy for developers to develop and test applications in the cluster.

I am not exactly sure about the pricing of Amazon EKS, but I think it is priced at the instance level, meaning EKS itself is not that high in price. However, whatever instances are used for Amazon EKS will determine the actual costs, particularly the traffic coming into the cluster.

Currently, I am not working with any software other than Amazon EKS, but we have plans to utilize some other applications, not just Amazon EKS, involving other services of AWS.

On a scale of one to ten, I rate Amazon EKS an eight.

Public Cloud

Amazon Web Services (AWS)

We use Amazon EKS mostly for deploying production workloads, and there are multiple AI models that we run on Amazon EKS.

My favorite feature of Amazon EKS is the ecosystem that it provides, including the integration with S3, along with EBS, and the networking that is smooth to run Kubernetes.

I have experience with Azure, and in comparison to Azure, a downside of Amazon EKS is that even if you want to deploy a dev workload or do some experimentation, we have to pay the charges for the control panel with no free option.

Additionally, I have faced many issues while configuring the node groups and the whole configurations; bringing up the nodes was a bit hectic, and I was not able to determine which node was failing and for what reason.

Specifically, the pricing for the control panel of Amazon EKS is hefty, and there is no cost-cutting that can be done on that side.

I have been using Amazon EKS in my career for four years overall.

Amazon EKS is pretty stable, and I have not seen any lagging, crashing, or downtime.

Amazon EKS is good in terms of scaling.

I have contacted technical support and customer support for Amazon EKS.

Positive

I have used Azure EKS, Civo, and also experimented with GCP as alternatives to Amazon EKS. If I have to rank between all three of them, GCP comes at number one, Amazon EKS comes at number two, and Azure EKS service comes at number three.

On the costing part of Kubernetes, Azure is beating Amazon EKS since I can do some experimentation without paying for the control panel; I can just pay for the node groups, which is an area where Amazon can improve.

From my point of view, the initial deployment of Amazon EKS is difficult.

I had to configure many components, such as IAM policies and other things; it was not a simple click-through process. The major issue is that there is no single point where I can see all the logs; while there is CloudWatch, it is not easily accessible, and you have to go through a hectic process to search and find information. There is nothing where you can go and click to get all the logs in a single place.

Amazon EKS requires maintenance on my end to continue functioning; we have to do upgradation from time to time since every Kubernetes version is only valid for one year.

On a scale from one to ten, I rate Amazon EKS a seven out of ten.

Public Cloud

Amazon Web Services (AWS)

I usually work with AWS tools focused on infrastructure deployments, onboarding new customers to the cloud, and offering the best practices across infrastructure, networking, security, monitoring, and availability, discussing high availability solutions and implementing the best practices over these. That's mainly my scope. For the development part, when it comes to services such as functions, Lambda functions and X-Ray and development services, I actually interfere with them in the deployment part and not for the configuration or the development part.

I've built a tool that can manage all these resources, whether it's on Microsoft Azure or Amazon Web Services or Oracle itself. This tool is efficient when it comes to assessments, assessing the environments for customers, getting the best security practices and measurements across the environment the customer has, having a cost optimization component that can be used to optimize the cloud environment. It covers automated deployments that you use with a user interface, so you don't have to write any code while deploying complex scenarios.

Regarding my experience with Amazon EKS, I have a complete solution for deployment as well. The tool is really powerful and can be used to do various things. I'm involved in the infrastructure, networking, and deployment part, so deploying these resources is one of my daily responsibilities. I use this tool to deploy all of these.

The deployment process for Amazon EKS is straightforward; you don't have to do anything basically. You just have to get the right image and the normal operation for Amazon EKS.

The best features of Amazon EKS involve the orchestration, which may be the concerning part of each customer when it comes to Amazon EKS especially. The automation part, the deployment and monitoring part, the security as well, having the connectivity going private or public, or using Kubelet are various aspects that users should be aware of, providing good experience while discussing these options with customers.

The integration capabilities of Amazon EKS seem fine, but it can be challenging using AWS services compared to other cloud providers, for example, Microsoft Azure. From using both platforms, Microsoft Azure offers more simplicity while doing complex deployments. AWS offers the same solutions; however, it seems more complicated when it comes to independent resources, where you need to establish dependencies before doing the actual resource deployment. This part needs an automation layer that already exists with the Microsoft Azure portal, which facilitates everything for the user experience.

I don't see much room for improvement for Amazon EKS; the Kubernetes technology is the same across all cloud providers. Most customers focus on the main common features they will use, such as the monitoring or the orchestration part, which is their main concern when it comes to this service specifically.

I have experience using Amazon EKS for approximately six years.

Regarding technical support from Amazon, I never personally experienced it, but the team I'm handling has faced their support, and they indicated they're quite good, but not on the first level part.

Positive

I have definitely seen an ROI with Amazon EKS. I developed a tool for cost optimization that can cover all of these, even with better approaches than the cloud itself. The tool I developed uses the native AWS recommendations, so ROIs and any saving plans that can be offered are included within the cost optimization. However, we've added our experience component upon using these resources as well.

For example, AWS will never tell you that you have to delete a virtual machine or an EC2 instance. However, our report can detect the stopped instances and provide a recommendation for the customer that for cost saving, they can use a backup or snapshot for this machine, and delete it. If they need to restore it, they can do that, or they may have to remove it if they're not using it.

In terms of pricing for Amazon EKS, I think it's quite reasonable. If we compare the cost to other providers, with providers such as Oracle, it will be much higher in cost. When comparing it to Microsoft Azure, it seems similar, with some variations. On a scale of one to ten, I rate Amazon EKS a seven out of ten.

Amazon Web Services (AWS)

From AWS, I use many services, but mostly my work revolves around Cloud Native, specifically Amazon EKS. Kubernetes is my area of focus and expertise. Most of my expertise is around Kubernetes and Cloud Native technologies. This is why I don't call myself a full cloud offering expert, but I mostly focus on the Kubernetes usage with other OSS solutions around K8S. It's not really a niche; it's huge.

I handle both application workloads and data ingestion workloads.

Based on my experience, the best features are backed up with extensive security that AWS allows and EKS is firmly integrated into their entire AWS cloud offering. The second feature is the ability to do what we call an in-place upgrade (upgrading an existing cluster), which is a very strong capability. Additionally, the ability to integrate other add-ons such as service mesh exists, but I don't use it heavily. The ability to use all EC2 node options, including GPU options, works quite efficiently.

The freshness of the Kubernetes versions is the most interesting aspect around CSP's Kubernetes offering; it's about how close they are to the latest and greatest of Kubernetes. GCP is the leaders in that area, but Amazon is quite close behind, which is very important.

It is definitely helpful to streamline the application deployment process.

Regarding the flexibility part, if I want to use something such as Kong/Linkerd service mesh or other solutions, most of the CSPs bind you to their own solutions rather than allow other options to be made and integrated with, and this is what I mostly miss in their part.

In terms of built-in observability in Amazon EKS, I know it's mostly about the great integration with AWS itself. When I want to integrate it with any Grafana or Prometheus solution within AWS, things work efficiently with IAM. However, when I want to cross the boundary of the CSP, that becomes an issue. Integrating some open-source solutions works, but I need to work really hard for that.

The major area for improvement I've seen involves deep diving into one CSP with no equivalent solution elsewhere. The most important consideration is about the pricing and the flexibility of moving and building a multi-cloud environment for most customers. The issue is that when CSPs try to lock you in, flexibility becomes the most critical aspect.

Amazon aims to put you in a very Amazon-centric environment, but you need to be aware when you're using Amazon EKS that you're not locked in. The major paradigm for customers with maturity in using cloud solutions  is to avoid vendor lock-in. Most early adopters understand this, but the main mass, such as the banking companies I work with, aren't in the same state of mind; they need to build everything from a Cloud Native perspective with as much OSS as possible.

I am still using all these technologies.

I would rate stability as nine out of ten.

I would rate scalability for Amazon EKS as nine out of ten.

For technical support with a business plan, I would rate it as nine out of ten.

If support is not paid, I would rate it as six out of ten.

This difference is mainly because of the response time.

With business support, I rate the solution overall as nine out of ten.

Positive

Considering the pricing of the product, I think it's affordable because it's mostly about EC2 stuff, and the control plane is not too expensive, taking into account what they do behind the scenes. Managing my own stuff in an on-prem environment helps me say that it's quite inexpensive in that aspect. The control plane is cheap, but the pricing of EC2 remains the same. I mostly don't prefer using EKS Fargate - managed containerized environment because it makes the devops team dumber and allows vendor locked in; it prevents me from managing my own infrastructure - scaling and fine tuning of resources' usage. Using margate as Autopilot in GCP and other products makes me more inclined to be locked in since it provides many features without the need to think much, but eventually, that's how the CSP will lock you in.

The integrations with IAM and Elastic Load Balancing are fundamental aspects. EC2 is the most important integration, and IAM is very strong in Amazon EKS, stronger than in other clouds. However, I need to compare it regularly as this landscape changes daily. The ELB and all the load balancing capabilities are quite strong in Amazon architecture and Amazon EKS architecture as well, so it integrates efficiently. I miss the flexibility to use other options, but I understand why they integrated it so tightly into their platform.

This isn't only an Amazon issue; it also occurs on GCP and other platforms, including Azure.

Overall rating: 9 out of 10.

Hybrid Cloud

Amazon Web Services (AWS)

My main use cases for Amazon EKS are securing the clusters and providing mesh gateways between the clusters.

The features that I find useful in Amazon EKS are Istio, Webhooks, service accounts, and ReplicaSets with different service accounts and accounts that we work with.

The main benefits that I received from using Amazon EKS are that it is a managed cluster and offers simplicity.

I am not the right person to ask what could be improved in Amazon EKS to make this tool better for the next release. A continuation of the managed pieces would be beneficial because there is no integration of clusters. They are all separate with no real managed cluster type of capability.

I have been working with Amazon EKS for about 3 and 1/2 to 4 years.

The initial setup for Amazon EKS is not straightforward. Kubernetes is not an easy technology because there are many technologies in the cluster. You need to understand infrastructure code to deploy it and understand all of the requirements alongside it. You cannot simply request deployment of EKS clusters as it does not work that way.

I would rate the setup for Amazon EKS as a three because I need to have other technologies and other tool sets to make it work. I cannot just go through Amazon's console and request a three-node cluster deployment because that does not work.

Regarding stability, Amazon EKS is stable. Once it is up, it works. I would rate it as a nine.

For scalability, Amazon EKS is scalable. I would rate it as a nine.

I have never contacted customer support for any issues on Amazon EKS.

Neutral

The solutions I evaluated before working with Amazon EKS include Grafana, Prometheus, K9s, Istio, and Consul.

The main benefits in Amazon EKS compared to those tools are that it is a different tool set completely, and they provide better visibility and connectivity.

The initial setup for Amazon EKS is not straightforward. Kubernetes is not an easy technology because there are many technologies in the cluster. You need to understand infrastructure code to deploy it and understand all of the requirements alongside it. You cannot simply request deployment of EKS clusters as it does not work that way.

I would rate the setup for Amazon EKS as a three because I need to have other technologies and other tool sets to make it work. I cannot just go through Amazon's console and request a three-node cluster deployment because that does not work.

I suggest understanding the entire form before understanding Kubernetes. I would rate Amazon EKS as a seven out of ten because Kubernetes across all CSPs is complicated. I do not think it is an easy technology to give it anything more than a seven.

Public Cloud

Amazon Web Services (AWS)

My main use case for Amazon EKS is for implementation and sustainable services and microservice application on a critical structure and services deployment.

On our application, we have more than 20 services and microservices such as authentication, login, account management, a notification service, and a billing service, which all work together to structure a heavy, useful application.

The best features Amazon EKS offers are scalability and deployment control, the ingress configuration regarding path pattern and host header to get all the services and microservices, and the HPA configuration.

The biggest difference, or the most important aspect to me, is the scalability, because you can easily scale any service or microservice to handle security during high changes in connection flow, and it is useful for the application and helps day-to-day by giving us reliability and stability so we can perform all maintenance and deployment of our system.

Reliability is a very important thing. Security and operational consistency are very important aspects, and the flexibility offered in node management and network options is also valuable. Amazon EKS is a service that is reliable and scalable, and it gives us a solid and dependable solution.

I think sometimes the documentation is not so clear and not so fast to provide more in-depth instruction and examples of bigger and critical implementations, so some difficulties for us sometimes take a lot of time to understand, test, and to put into production with security and guarantees.

I have been using Amazon EKS for almost five years now.

I advise doing a POC first and getting all the details, testing, and having a very good alignment between DevOps and development departments, and prepare all the CDN and how the connections get into your cluster, and how you configure your ingress and how to prepare every service or microservice to receive that with secure and optimized code, process, and communication with other resources. I would rate this product an 8.

Private Cloud

Amazon Web Services (AWS)

I deal with application development. I have used AWS services for configuring elastic search, deploying in pods, and using the CI/CD pipeline with Jenkins to build and deploy applications.

Amazon EKS allows upscaling and downscaling by reallocating resources. It is possible to configure everything, monitor applications, and perform routing in pods, securing the application with whitelisting. Datadog can be used to trace applications for performance issues or errors. It is an effective platform for cloud operations on AWS, similar to its counterpart on Azure.

There is room for improvement in making Amazon EKS less error-prone when writing on the YAML file. A UI could help generate config files, simplifying the process for developers who are not architects. It is very time-consuming, and companies often expect developers to do everything, which can be overwhelming.

I have used AWS for three or four years, specifically for Amazon EKS for two years.

It is not easy to configure Amazon EKS, and it requires very detailed attention to configuration and deployment. It can be error-prone and time-consuming to redeploy until a stable configuration is achieved.

Amazon EKS is effective for scalability, providing features for upscaling and downscaling resources as needed.

Their technical support team is good, but they do not instruct on what to do. Having to know what questions to ask is essential. The documentation is adequate but could include more practical insights.

Neutral

The pricing structure is beneficial for large companies who pay for what they use, but it is not affordable for startups. Offering a free version could help small companies.

Overall, Amazon EKS is a great technology, but the knowledge required to use it is scarce. It is a skill in itself, and developers must undertake multiple roles, which can be difficult. I rate Amazon EKS a seven because it is not easy for developers to configure without a solid base of knowledge.

Public Cloud

Amazon Web Services (AWS)

The main reasons for using Amazon EKS in our use were third-party solutions that were distributed as Helm charts. We were using Rancher to manage multi-cloud deployment for unification. We are also using it for evaluation purposes, building customer pilots and prototypes. Sometimes it is easy to make the build chain run through and come out as images and deploy them into Kubernetes.

It completely depends on use case. If you have got a very dynamic or a requirement to scale very fast with nodes, then Amazon EKS is a very good choice because you have got that reach and the ability to scale quickly. But if you have got a fairly static load, it becomes quite expensive quite quickly. They are expensive CPU cycles.

The main benefit of Amazon EKS is its rapid deployment. The fact that we can deploy it very quickly with infrastructure as code and then tear it down again when we are finished.

There is no real advantage to us from Amazon EKS because the advantage is the fact that we have a unified management product so we can deploy concurrently into multiple clouds and on-prem out of one pane of glass. That is the key thing there. As far as the development and presentation, sometimes it is easy just to load it up through kube control, sometimes you put it through a GUI control in front.

We have not been using it from the point of the application using the IAM. We have been using it because quite often our customers are tied back to usually Entra ID and things like that.

The only concerns I had with Amazon EKS were related to cost, the usual problem you have with cloud. It is fine if you can exploit it for dynamic loads, bring it up, get rid of it again. That is where its strength is. You pay for that premium, but as far as running the thing under constant load, it is a very expensive way of deploying.

In the early days, there were a couple of vulnerabilities exploited from the single control plane per region. So there is nothing stopping me deploying multi-region, and that means multiple control planes. So I could deal with that, the infrastructure handled the criticality. The only thing that I could possibly run into a problem with, which I have not had to at this point, but architecturally, is with regulated technologies, banks, that sort of stuff where you cannot be single provider sensitive.

We have been dealing with it from the beginning almost, since 2019.

Only in the past I think it had issues. The fact that regions only had a single control plane left a little bit of vulnerability in there, certainly in the early days, but I do not think that matters now. They seem to have solved that.

I had no problem. It was stable. Very stable.

It was very easy to scale.

The current stuff I am working with has been Kubernetes and building out operational software using Kubernetes. I was actually reviewing Nutanix as an option for some of the stuff I was building out.

Mainly on-prem, we are doing production work with a number of customers. We support them, we run an operational arm as well. I have been involved in platforming on Kubernetes, but we happily support any variant. We are cloud agnostic. So these distributions, we would use Amazon EKS or AKS, but not for long.

The driver in Rancher, as long as I do not have anything extremely different or complex, works completely the same whether I am driving the application onto Amazon EKS or onto a local on-prem.

We have not been using the automated patching. If we were in anger, we do not run the stuff long enough in Amazon EKS at the moment. Really, it is just up in demo and then torn down again. A lot of the stuff is being driven from other automation anyway, more infrastructure as code stuff. So that actually just gets driven completely in there.

I think that Amazon, every other provider, is adapting to the changes in the market now because the major cloud benefits are now fully saturated. Nobody else is going in for those benefits. They are starting to hit the reality of regulated technologies that are high value cannot be under a single provider. So a single cloud provider is not sufficient to support critical industry anymore. You have to have either multiple cloud or hybrid just to meet regulation in the future. So that constrains some of the flexibility. But the clouds are all working towards more on-prem extension, that sort of thing to make it more feasible.

I would rate Amazon EKS a six out of ten. I have a particular penchant for not actually overscoring anymore because of the way that people use this stuff. In other words, I consider adequate doing what it says they claim it to do. So that is a five or a six as they did what they said they would do. There is nothing wrong with that. It is what we agreed. I paid for it, they delivered it. I am satisfied.

Hybrid Cloud

Amazon Web Services (AWS)