Amazon EKS Reviews

I am using Amazon EKS as an integrator.

Regarding Amazon EKS integration with IAM, I do not use it.

To use Amazon EKS as a cloud provider and as a Kubernetes cluster managed by a cloud provider, it offers more benefits because you don't have to configure the cluster on your own. You can use the default configuration and just set the right networking space, set the subnet, and a few other things, but you don't have to raise up or configure your own cluster.

Self-healing nodes help to minimize administrative burdens in the organization. It helps to keep the nodes up and running. Then you can use other solutions to minimize costs or to keep the nodes running most of the time.

You can use Amazon EKS to raise up clusters and deploy applications in the cluster. The cluster is managed by Amazon, so you don't have to configure it. You can use the basic configuration of Amazon, and you don't have to interact with etcd or with the Kubernetes most inner parts. It's more simple to use.

Amazon EKS can give you more flexibility to configure on their own. In general, it's a good product. There are many different products that can fit the needs of the user or the customer in every part of AWS. In Amazon EKS, they can give a class that can be more configurable from the user or expert user rather than just using the default EKS.

Amazon EKS support for AWS tools integration has an impact on application development and management because everything is deployed on the cluster. You have to debug the various pods in Kubernetes. There isn't a direct impact, but there is an impact because everything you deploy through the pipelines goes to the cluster and there you have to integrate the cycle.

The main problem or area for improvement is flexibility in configuration. This is the only concerning part and nothing apart from this.

I have been using solutions similar to Amazon EKS from other vendors. I used GKE from Google, the cluster of Azure, and I also used KMinikube. Of course, it's not the same thing, but in general, it can be compared. For testing, K3s are just different distributions. In general, I have used other cloud providers.

It's quite easy to install Amazon EKS.

In Amazon EKS, I see it as a stable product. I don't see any particular issues in terms of nodes or performance.

I believe Amazon EKS is scalable.

I have never used the technical support from AWS.

I see return on investment with Amazon EKS. You can save in terms of time because you can raise up a cluster or more nodes, and you can raise up the storage of the particular node in a few minutes. You don't have to take care of managing the machines directly. There is significant time-saving. You don't have to take care of the rack system because AWS has a team that works that part. You have just to pay. In terms of price saving and money saving, it depends on everything, but in general, you're going to save money.

In general, the price of Amazon EKS is expensive, but it depends a lot on the user knowledge of the tool and how we can manage the cost, which solution offers better, which solutions they can use to reduce the cost. For example, the different VM types, the Preemptible VMs or the Preemptible nodes, or you can pay one time for the use, you can reserve the machines. There are many different ways to reduce the cost.

I see big differences between Amazon EKS and GKE. The way you install the cluster is different. In GKE, when you install the cluster, it raises the nodes for you. In AWS, you can install the cluster and then you have to raise up the node using Auto Scaling Group or whatever. It's more integrated maybe. Also in terms of documentation, Google is different from Amazon.

Regarding the automated patching feature for Kubernetes clusters in Amazon EKS, I don't know any patching feature.

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

Public Cloud

Amazon Web Services (AWS)

My main use case for Amazon EKS is to host one of my AI agents which I built recently in my company. I use Amazon EKS to host my AI agent, which is a sprint report agent that fetches the company's data from Jira and prepares a sprint report for the complete team. The agent runs on Amazon EKS for high availability and reliability, hosted on nodes, and it is running on a GPT OS's model in the back end.

I have designed this agent for high availability on Amazon EKS because if I hosted it on any other platform, there would be chances of downtime. I have set it up in such a way that if there is any downtime, a new node is already up and running so that my use case is not affected and the users can use it seamlessly without any issues.

The best features Amazon EKS offers in my experience are its reliability and high availability, and also the support that AWS provides. The reliability and high availability have helped me specifically because there were some configuration issues at my end for the agent, which caused it to go down repeatedly. Due to the high availability features, every time a node downscaled, a new node was automatically scaled up, ensuring that the AI agent was up. I was able to check the logs and correct the issues accurately thanks to that high availability. Also, AWS support is very helpful; whenever I face issues regarding costing or anything else, I just create a ticket and they assist me in resolving the issues.

Amazon EKS has positively impacted my organization by improving the efficiency and working capacity of my team. It improved efficiency and working capacity because, based on how Amazon EKS works, we are more calm regarding functionality. The reliability allows us to focus on many other tasks, as the infrastructure is maintained by Amazon EKS; therefore, we can divert our attention to other tasks and perform well there as well.

Functionality-wise, Amazon EKS is acceptable, but navigation-wise, it could be improved in the AWS console; it could be more interactive and more intuitive for new users. Also, the pricing can be reviewed as it is sometimes a bit pricey, particularly regarding the extended support when new version upgrades occur that we cannot implement directly due to production workloads, as clusters running on extended support cost six times more, which is something that could be reduced.

I believe documentation could be improved on the AWS website so a new user who is starting with Amazon EKS could work much better with it.

I have been working in my current field for three years.

In my experience, Amazon EKS is stable.

The scalability of Amazon EKS is good.

The customer support of Amazon EKS is good. I would rate the customer support on a scale of one to ten as a seven.

Positive

I have seen a return on investment because the reliability has helped me save time; I can rely on Amazon EKS's reliability and then divert my attention to other tasks, so it has definitely saved my time. I estimate that my team and I save roughly one to one and a half hours a day since using Amazon EKS.

Regarding pricing, setup cost, and licensing, the pricing for the cluster part is a bit higher; the setup cost is acceptable, but the licensing part regarding extended support is also a bit pricey, which I think can be handled or reduced.

Amazon EKS is a good product; if you are starting with Kubernetes, it is a good choice, but the pricing is a bit substantial, so you should review that. Also, regarding the support, there are sometimes cases where you need to upgrade your AWS plans for particular support, which can also be a bit pricey. I would rate this product a seven overall.

Private Cloud

Amazon Web Services (AWS)

As integrators, we are the user of Amazon EKS. Our customer's main use cases for Amazon EKS are mostly internal services automation and development and deployment automation, which we are using for the digital applications of our customers in the AWS cloud.

The most valuable features in Amazon EKS include a suite of different services, such as code versioning, pipelining, code deployment, and code quality checks; we are using the total suite of the Amazon EKS.

From a project management standpoint, the automated node provisioning feature in Amazon EKS helps to streamline the application deployment process because the benefit I see with this product is that our deployment turnaround time reduces considerably, and all compliance standards are met. Code quality is maintained, and there are specific indicators designed in the product to identify quality issues with minimal effort. The Agile mode of project execution methodologies can also be implemented due to the code version controls and pipelining controls.

Most importantly, the deployment side of code releases and release management features are maintained without major hassles, within a short span of time, and without delays to customer experience. From both operational management and project management angles, these tools address human as well as programming side hurdles, eliminating most gaps and enabling timely project execution without surprises and ensuring quick turnaround time while meeting delivery deadlines.

Amazon EKS's deep integration with AWS services such as Identity Access Management impacts the approach to security and compliance because it integrates with IAM authentication and the multi-factor authentication process, allowing access only to those who need it.

I recommend that Amazon EKS could be improved by integrating AI intelligence with its components because EKS or the Kubernetes cluster has not yet undergone an AI wrapper. An AI component integrated into Amazon EKS, such as failure analysis and intelligent recommendations when failures happen, would be very helpful. Although automation is present, this AI feature would enhance the overall capability.

I have been working with Amazon EKS for almost four or five years now.

I have not faced any challenges with Amazon EKS; it's good and quicker. Initially, implementation can be a bit time-consuming, but once set, it becomes a 'code it and forget it' sort of environment.

I have no complaints about the stability of Amazon EKS; it is good, with no concerns at this point in time.

Amazon EKS is good regarding scalability; it suits conventional services and has room for improvement with upcoming agentic AI and GenAI resources.

My experience with Amazon support is good; we always had a good association with them, so no concerns on that. I would rate the support of Amazon EKS above seven.

Positive

Customers have seen a return on investment with Amazon EKS because they are happy and see value in the services; however, as the volume grows, the OpEx cost also increases, so any respite on OpEx cost for customers with exponentially growing volumes would be helpful.

Regarding the cost of Amazon EKS, I would say it's relative to the organization based on release management processes; for big organizations where customer experience matters, such as in the retail segment, the cost can be very high due to numerous daily changes. For companies in telecom and retail, as Amazon is a pay-per-use service, our usage levels are high, so I would desire if Amazon could provide certain discounts or credits for customers who utilize a lot of resources.

Our customers use the solution on the Amazon AWS cloud. They purchase Amazon EKS through AWS only.

For those looking into using Amazon EKS, my advice is that it is a good product, although the downside is that if the volume grows, the OpEx cost increases significantly. I would strongly recommend it for small and medium companies. For big companies with more releases, it also attracts more OpEx costs, so if there is a mechanism to control costs, it can be suitable for everybody.

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

Public Cloud

Amazon Web Services (AWS)

The use cases for the product involve provisioning of infrastructure and auto provisioning of infrastructure.

I have managed on-premise deployments in my use case with a Helm chart.

The biggest advantages of Amazon EKS include load balancing, auto scalability, and platform integration.

The solution includes automated node provisioning features.

The integration with AWS services involves platform services only.

We usually get deployed and only need to tweak the source code; however, I think the monitoring part and observability part could be improved.

I have been selling it for almost two years.

The scalability of Amazon EKS deserves a perfect rating of ten.

The technical support from Amazon deserves a rating of ten.

Positive

I would rate the ease of installing Amazon EKS in the middle area, giving it a five.

I have moved to pre-sales activity now.

I am selling Kubernetes Engine from Amazon.

I can rate Amazon EKS as nine because I just need to see some improvement.

I want to be a reference for Amazon.

The overall rating for Amazon EKS is 9 out of 10.

Public Cloud

Amazon Web Services (AWS)

I use this to develop my products. I use it internally in my company and in the other projects I have been working on for the deployment and managing the services which I'm deploying into the Amazon EKS infrastructure. I have not actually been involved with automated patching, as my role has predominantly been as a developer setting up how we deploy our applications into Kubernetes. That's primarily where I've gained experience, not on the server management side where the patching is done, so I'm not sure how the patching works or what benefits it could offer in that context. However, I can discuss how I manage my CI/CD pipelines, application deployment, and how I use Amazon EKS for deployment. That is the part I have experience with.

I have been using Amazon EKS, and I started with ECS first, which is the Elastic Container Service where I can deploy my workloads. ECS is also one of other managed services from AWS, but it is not supporting Kubernetes. We wanted a platform where we could have an orchestration platform for Kubernetes. Hosting our own Kubernetes server is a very tedious job. Kubernetes itself is a very complex tool to manage and requires a lot of resources and knowledge to build a working solution. That's where Amazon EKS comes into the picture as a managed service built on top of a Kubernetes engine, offering many tools, such as CLI integrated tools or through their console to quickly set up a Kubernetes cluster, which otherwise is a tedious job.

With that offering, it is very easy to set up the Kubernetes cluster in Amazon EKS, and it is very easy to manage the nodes we have there, such as what instances we need. Since it's an AWS offering, we select a variety of EC2 instances available, and it integrates with it nicely. The same applies to the infrastructure as a service tool, IaaS, such as Terraform. It is very easy to create and manage Amazon EKS clusters through Terraform. Overall, it offers a lot of tooling and saves a lot of time compared to setting up and managing a Kubernetes server ourselves.

A specific feature of Amazon EKS is that Kubernetes is open source, and all its capabilities are based on that. The main advantage is launching and managing a Kubernetes server becomes very easy, as I receive out-of-the-box support for other AWS service integrations with Amazon EKS. For example, services such as AWS IAM directly integrate whenever I want to set up access control or security measures on my Kubernetes server. EC2 offers out-of-the-box support when setting up Kubernetes nodes. All this setup we need to do otherwise becomes much easier with Amazon EKS.

Regarding measuring the impact of Amazon EKS on my organization's ability to manage complex workflows effectively, there are measurable metrics we use. Whenever we set up any project, it is crucial to ensure we understand the availability and scalability of our applications. When I set up any application, I look at how we will be able to scale whenever there is a requirement for higher loads. To measure the Amazon EKS platform's effectiveness in this regard, I evaluate the different methods available for scaling the application. For instance, based on CPU and memory consumption, I can scale or use scalability tools such as KEDA. KEDA helps us scale based on various factors, such as the number of requests my application receives or the load on my service based on metrics. These tools can be easily installed on my Amazon EKS server without restrictions. Availability is crucial when setting up a Kubernetes cluster, especially when designing for a global audience using Amazon AWS. The options to configure multi-region and multi-AZ setups are incredibly valuable, as these features ensure high availability without complex traditional setups required for on-premise hosting.

One area I observed during setup was that while managing it through CLI and Terraform, there are many possibilities for setup and infrastructure updates. However, I believe the console experience could improve. In the AWS console, when trying to set up an Amazon EKS cluster, there were limitations on certain features I encountered a few months back while checking. EKS frequently updates, so I don't know if there's a new release. However, I found some features that I could not manage through the console, requiring me to use CLI or Terraform. It would be beneficial if we could have all features supported through the console, providing full management capabilities there.

I have been working with this tool for around two years now.

My current organization has not been using self-healing nodes, but I have used it in some earlier projects and organizations I worked with. When we decided to move away from containerization services such as ECS, we wanted a better orchestration platform that could easily handle those requirements. Kubernetes comes with many features for scalability, which otherwise we would have to manage ourselves with scripts. While Kubernetes is a good choice, it comes with its own learning curve, and understanding all the details is a big task. Services such as Amazon EKS, or maybe GKE for Google, provide the confidence that we will benefit from the orchestration framework that Kubernetes offers while also setting it up and managing it easily. We gain all the advantages that Kubernetes has as an engine without having to invest a great deal of time learning and configuring everything thanks to managed services such as Amazon EKS.

Regarding technical support, I recall one instance with Amazon EKS. I faced an issue with configuring pods in EKS that required access to other AWS services, such as IAM roles or S3 buckets. The setup was through OIDC providers in EKS, which set up trust relationships with IAM roles. There was a problem with OIDC provider setup a few years back when EKS was newer. I reached out, and I received good support when I submitted a ticket for the issues with the OIDC provider. They helped resolve the issues related to the trust relationship, identifying mistakes that needed fixing.

Positive

In my current company, I don't use it, but in my earlier company, we started with ECS, another AWS offering where we deployed our containers. However, as our deployment expanded, the limitations in scalability prompted us to explore better options. We began to reach a point where more than 30 or 40 instances of our services were running, and there was a need to support these across different regions. ECS offered some level of scalability, but it was not as customizable as Kubernetes, so we decided to transition from ECS to Amazon EKS to harness its full capabilities.

Using Amazon EKS as a cluster is free. The pricing only applies when I add the instances and set up nodes. For instance, when I add memory-optimized nodes, the applicable AWS pricing for those instances comes into play. Essentially, the pricing revolves around the nodes added, not the other configurations I'm attempting to set up.

Regarding the pricing of nodes, I find that it generally offers good value. I'm not certain what the comparative costs look against other platforms, such as OCI from Oracle that is known to offer lower pricing, but it ultimately depends. For example, AWS has recently introduced Graviton-based servers, which claim to be cost-saving, although I haven't used them myself. AWS provides several options, allowing me to choose configurations that suit my needs regarding CPU and memory. While I don't have firm details about enterprise pricing options or upfront reservations that may provide discounts, what I appreciate is the flexibility in selecting from various instance categories to meet specific requirements.

Based on my experience with Amazon EKS support, I would rate it a nine out of ten overall.

Public Cloud

Amazon Web Services (AWS)

I use Amazon EKS mainly for deploying my application onto the Kubernetes infrastructure, which is provided by the underlying Amazon infrastructure.

I have many services, many applications, and many web services and web applications which are deployed using Amazon EKS across different regions in Amazon web service locations and data centers.

Other than deploying applications onto Kubernetes infrastructure using Amazon EKS, I don't have any other use cases for this tool in my current organization.

Amazon EKS has very good scalability with 100% uptime and zero latency.

Amazon EKS is the most cost-effective solution that I am using currently. If I want to reduce my downtime, I can deploy it in a multiple region architecture, which can reduce the downtime.

It is a cloud-based solution which is managed by Amazon, a global cloud services provider. I have observed very negligible issues while running my applications on Amazon EKS.

It is very pocket-friendly, cost-effective, and the setup is very simple.

If you are running a few applications that require high scalability, you can go for Amazon EKS. It is a very good tool if you want a managed Kubernetes service. It will definitely work wonders for your project.

Currently I work for a financial global giant where a millisecond latency costs around a million dollars. With Amazon EKS, I have a lot of benefits.

The only thing I feel is keeping Amazon EKS updated with the current trends and requirements of the global giants which are using this tool.

I have been using Amazon EKS for the past three years. It is very brilliant.

I have worked on several improvements, particularly regarding instances when Amazon goes down, which is the only time I see issues in Amazon EKS.

It is pretty good and pretty stable.

I have not experienced any scalability issues.

I have not had any issues with customer service.

Negative

I have not used any previous solutions.

I don't have any alternate solutions.

It is already a great tool. It is already a very good tool in the market. I would rate this product a 10 out of 10.

Public Cloud

Amazon Web Services (AWS)

I mainly use the service for competition purposes, specifically for a specific competition.

The tools we are trying to see align with R&D's use cases, and then we are going to integrate them.

It provides benefits in terms of operational efficiency.

I consider Amazon EKS to be cost-effective.

The way we are using Amazon EKS is quite good, and it is fulfilling all the purposes we wanted to use it for until now. All the tools we are using in this project are AWS tools, and we are fully satisfied.

Nothing comes to my mind right now that could be improved in Amazon EKS, and I am not facing any issues.

I joined this project later, but I have been working with AWS for more than one and a half years now.

I have not contacted AWS technical support in this project, but in previous projects, we contacted them twice regarding database and other issues. They are quite good, and because it is a build project, we received immediate support within twenty-four hours. During the call, issues were solved immediately.

Positive

I have not worked with that tool currently or previously in Germany as we were not using it at that moment.

I am currently conducting POCs.

I have about four to five AI tools, with around one month of experience so far.

This is a new initiative that has not happened before.

I do not have hands-on experiences, and I have not tried Google Gemini yet. It is just a new feature we are trying to implement with AI.

With the POC, we are trying to figure out all those things, as it has already been done as part of POC, so I do not anticipate any issues later on.

On a scale of 1-10, I rate Amazon EKS a 10.

Amazon Web Services (AWS)

I use Amazon EKS for managing production environments. I have worked for different companies over the past three years, managing microservice applications on Amazon EKS to deploy application code to the environment, including the production environment. We use DevOps methodology to deploy these services.

The most beneficial aspect of Amazon EKS is that it helps manage the Kubernetes master node, so I don't need to maintain the master node, including tasks like upgrading. This allows me to focus on business code. If using services like Fargate, I only need to maintain my workload, simply uploading code that will be deployed to the Kubernetes cluster. This is especially beneficial for startup companies that lack the technical resources to manage the Kubernetes cluster. Furthermore, Amazon EKS allows me to utilize Kubernetes cluster-level expansion. If there’s insufficient resource on a machine, the cluster can automatically expand to add new nodes.

Although Amazon EKS is popular, there are areas for improvement. It could support more scenarios and plugins. Currently, some third-party plugins, like certain network plugins such as Weave CNI, might not be fully supported. 

I have been working with Amazon EKS for more than three years.

I haven't found any performance issues with Amazon EKS so far. To avoid potential performance issues, it is important to plan resources initially, ensuring there are enough compute resources like nodes to host applications.

Amazon EKS is very scalable, but scaling can sometimes cause trouble. When Amazon EKS scales up or down, there might be occasional intermediate pod interruptions, though it's rare.

I have escalated some questions to AWS tech support before. I once faced a random issue where a pod abruptly shut down and restarted. Upon escalation, AWS helped me find the root cause. Overall, I would rate AWS tech support an eight out of ten.

Positive

I have experience with Azure AKS and some exposure to Google GKE. However, I mostly have experience with Amazon EKS.

When I first set up Amazon EKS, I faced challenges because there are different setup methods. Using the console does not align well with DevOps. It is better to use EKS CTL or Terraform's IAC tools. Configuring role permission policies is the most challenging part, ensuring Amazon EKS has access to different services or databases.

I have experience with Azure AKS and some exposure to Google GKE.

I would recommend Amazon EKS for large companies, especially banks, due to AWS's extended support for Amazon EKS, its availability, and reliability. Amazon EKS offers a strong solution as part of a full suite, but it should be integrated with services like Lambda for a complete solution. On a scale of one to ten, I rate Amazon EKS an eight because there is still room for improvement. The overall product rating is eight out of ten.

Public Cloud

Amazon Web Services (AWS)