It is challenging to host the applications in the existing VPC of the solution. They should include some essential configuration features to it.
Sr. Software Engineer at a tech vendor with 10,001+ employees
Good stability and easy initial setup process
Pros and Cons
- "It is a scalable solution."
- "They should include some essential configuration features to it."
What needs improvement?
For how long have I used the solution?
We have been using the solution for the last two to three years.
What do I think about the stability of the solution?
It is a stable solution. I rate its stability as an eight or nine. Although, it is difficult to find a stable version sometimes.
What do I think about the scalability of the solution?
It is a scalable solution. I rate its scalability as a ten. We can quickly scale the cluster as per requirements. We have medium and enterprise business clients using the solution.
Buyer's Guide
Amazon EKS
April 2025

Learn what your peers think about Amazon EKS. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
846,617 professionals have used our research since 2012.
How are customer service and support?
The solution's customer service is excellent. They also provide detailed documentation.
How would you rate customer service and support?
Positive
How was the initial setup?
The solution's initial setup process is straightforward. It takes two to three days to deploy it in any infrastructure. We require one executive for implementation and around two executives for maintenance.
What's my experience with pricing, setup cost, and licensing?
The solution is cheaper than AKS. Its license costs $73. The customers have to pay extra depending on the instances they want to deploy for hosting the application. I rate its pricing as a four.
What other advice do I have?
I rate the solution as an eight. I advise others to use EKS ETL instead of AWS command prompt while deploying it.
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator

Practice Director, Global Infrastructure Services at a computer software company with 10,001+ employees
Great provisioning and basic features with good technical support
Pros and Cons
- "The solution has very good basic features."
- "I'd like to see the solution add a service catalog."
What is our primary use case?
I have tried to host the enterprise content management application of IBM FileNet on Amazon EKS. That's the main use case.
What is most valuable?
The solution has very good basic features.
The provisioning is very good we use it for the containerization of COTS applications.
The product is stable.
If a company needs to scale the solution, it can.
The initial setup is simple.
We've found the solution's technical support to be helpful and responsive.
What needs improvement?
There isn't something that is unique or outstanding.
I'd like to see the solution add a service catalog.
For how long have I used the solution?
I've used the solution for quite a number of years. It's been around three so far.
What do I think about the stability of the solution?
We've found the solution to be stable. Currently, it's used on standard VMs. If we put it on Kubernetes clusters, it is highly reliable as well as easy to monitor, manage, and operate. It's great.
What do I think about the scalability of the solution?
The solution is absolutely scalable. There are many enterprises running their businesses on this.
I'm not deploying anything for customers or a certain number of users. I'm just doing it for my own purposes. I'm learning about it and I'm trying new things. I propose these ideas to customers for various solutions and the implementations are done by another team, the delivery team, later. I can't speak to how many people ultimately end up using it.
How are customer service and support?
Technical support is very good. There is no issue. There's no delayed response for their support. There's no lack of support. They are very helpful and we are quite satisfied.
How was the initial setup?
The initial setup is not overly complex or difficult. It's very simple, very straightforward. The instruction guides are all available and it's enough to get a user through the setup process. They are quite helpful guides.
What about the implementation team?
We have a professional services team that does the job day in, day out. That said, I do it for my learning and I practice something on my own too. Therefore, I am also very capable of handling the initial setup myself.
What's my experience with pricing, setup cost, and licensing?
We already have costs built into the service given by the particular vendor. If it is on-premise, we buy the software, and we pay some support costs and license costs. However, if it is on the cloud, it is a pay-per-use model.
What other advice do I have?
I'm an integrator of the solution.
The solution can be deployed both on the cloud and on-premises.
We are using the latest version of the solution at this time. I can't speak to the exact version number, however.
I would recommend this solution to others.
I'd rate the product at a nine out of ten. We're pretty happy with its capabilities so far.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
Buyer's Guide
Amazon EKS
April 2025

Learn what your peers think about Amazon EKS. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
846,617 professionals have used our research since 2012.
Solution Architect, DevOps Engineer at sonne technology
A solution with a robust cluster engine and good computing services
Pros and Cons
- "The most valuable feature is the cluster engine."
- "They should enhance the Jira integration."
What is our primary use case?
We just implemented the acquisition project for our cloud application environment, and we implemented Amazon EKS.
What is most valuable?
The most valuable feature is the cluster engine. It is also a feature in Kubernetes clusters, and we can't differentiate between the benefits in Amazon EKS and Kubernetes.
What needs improvement?
They should improve the security and include some cloud-native project integrations. In addition, they should enhance the Jira integration.
For how long have I used the solution?
We have been using this solution for about two years, and it is deployed on cloud.
What do I think about the stability of the solution?
It is a stable solution.
What do I think about the scalability of the solution?
Amazon EKS is scalable. When the usage increases, the EKS clusters immediately increase the number of ports and cluster nodes. Amazon EKS is ready for implementation, but the implementation depends on the number of clients. Our target is to increase our clients, and when that happens, the use of Amazon EKS will increase.
How are customer service and support?
We have not needed technical support.
How was the initial setup?
There is no installation required, but some implementation procedures and configurations are needed. The configuration is simple because Kubernetes manage it, and we do not drive all the Kubernetes clusters using a command line interface. We drive all the management activities with a user interface.
What's my experience with pricing, setup cost, and licensing?
It's a subscription and depends on the cluster nodes and other effects. There are many calculation criteria for licensing.
Which other solutions did I evaluate?
There are a lot of criteria affecting why we switched to Amazon AWS. In addition to its features, it has computing services and app store services.
What other advice do I have?
I rate the solution a nine out of ten and recommend it to others.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Straightforward setup and takes only 15 minutes to deploy
Pros and Cons
- "Initial setup is straightforward. It only takes 15 minutes to deploy."
- "The graphical user interface could be better."
What is our primary use case?
It's mainly deployed on a public cloud.
What needs improvement?
The graphical user interface could be better.
For how long have I used the solution?
I have used Amazon EKS for three years.
What do I think about the stability of the solution?
I would rate the stability as eight out of ten.
What do I think about the scalability of the solution?
I would rate the scalability as eight out of ten.
How are customer service and support?
I would rate technical support as eight out of ten.
Which solution did I use previously and why did I switch?
I have also used Azure. Azure has a better graphical user interface than AWS and is more user-friendly. I'm able to get all of the services we need on Azure.
How was the initial setup?
Initial setup is straightforward. It only takes 15 minutes to deploy.
Before setup, you need to understand the requirement, configuration, how many nodes are needed, and how much storage configuration is needed. You also need to understand the network requirement.
What's my experience with pricing, setup cost, and licensing?
The price could be cheaper. I would rate it as seven out of ten.
There are no extra costs in addition to the standard license.
What other advice do I have?
I would rate this solution as eight out of ten.
I highly recommend Amazon EKS.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Implementer
Sub Gerente Backend Digital Regional at a retailer with 501-1,000 employees
The tool is a good investment but needs improvement in customer operations
Pros and Cons
- "Amazon EKS is very scalable."
- "Amazon EKS needs to improve customer operations and technical support."
What is our primary use case?
We use Amazon EKS for our proprietary solutions and applications.
What is most valuable?
Amazon EKS is very scalable.
What needs improvement?
Amazon EKS needs to improve customer operations and technical support.
For how long have I used the solution?
I have been working with the tool for five years.
What do I think about the stability of the solution?
The tool's stability is high.
How are customer service and support?
We don't need technical support at the moment.
How was the initial setup?
The tool's deployment is not complex.
What was our ROI?
Amazon EKS is a good investment.
What's my experience with pricing, setup cost, and licensing?
The tool's pricing is good.
What other advice do I have?
I would rate Amazon EKS an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Software Engineer II at a computer software company with 201-500 employees
Excellent stability, with efficient speed , but the user interface is hard to find
Pros and Cons
- "The most valuable feature is the computing speed."
- "I would like to see the user interface improved because it is hard to find and not straightforward."
What is our primary use case?
Our primary use case is for distribution computing.
What is most valuable?
The most valuable feature is the computing speed.
What needs improvement?
I would like to see the user interface improved because it is hard to find and not straightforward.
For how long have I used the solution?
I have been using Amazon EKS for the past six months.
What do I think about the stability of the solution?
The current stability is very good.
What do I think about the scalability of the solution?
There is sufficient scalability.
How are customer service and support?
Our experience with technical support is hit or miss. They are really fast in responding but they do not always solve the main issue. Sometimes they do not have the proper training.
How was the initial setup?
The initial setup is quite straightforward.
What other advice do I have?
I would recommend that you have enough knowledge of Kubernetes because you can not have basic training for that. You need to know the main concept of Kubernetes, and it will be much easier for you to use Amazon EKS. I would rate Amazon EKS a seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Team Lead, Network at a tech consulting company with 11-50 employees
Recommended cloud solution with easy setup
Pros and Cons
- "The solution is easy-to-set up."
- "I'd like improved traffic handling and additional application details within the system."
What is most valuable?
The solution is easy-to-set up. It is quick, and the main management is conveniently maintained in AWS, eliminating concerns.
What needs improvement?
I'd like improved traffic handling and additional application details within the system.
For how long have I used the solution?
I have been working with the solution for three years now.
What do I think about the stability of the solution?
Amazon EKS is stable.
What do I think about the scalability of the solution?
The solution is scalable.
How was the initial setup?
The solution is straightforward to set up.
Which other solutions did I evaluate?
We are also working with VMware Tanzu.
What other advice do I have?
I would recommend the solution. Overall, I rate it a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
Solution Architect / Head of DevOps Engineer at a tech services company with 201-500 employees
Reliable, helpful technical support, and beneficial replication and scaling
Pros and Cons
- "We do not have to do a lot of administration, such as create virtual machines, or worry about our controllers or nodes going down because the solution is fully managed by Amazon."
What is our primary use case?
Amazon Elastic Kubernetes Service (EKS) solution integrates AWS cloud with Kubernetes. Kubernetes is an open-source container technology that is popular right now. It has the ability to replicate applications for scaling.
How has it helped my organization?
Having this solution on the cloud has allowed us to focus more on our business because we do not have to worry about our own infrastructure.
What is most valuable?
We do not have to do a lot of administration, such as create virtual machines, or worry about our controllers or nodes going down because the solution is fully managed by Amazon.
You are able to have your applications on the cluster which provides the ability to replicate and scale them.
For how long have I used the solution?
I have been using the solution for approximately two years.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
I have found the solution scalable.
This solution is used by the three-person DevOps team in my organization.
How are customer service and technical support?
The technical support is very good.
How was the initial setup?
The creation of the clusters only takes approximately 10 minutes.
What about the implementation team?
We did the installation and configuration ourselves.
What's my experience with pricing, setup cost, and licensing?
The solution is more expensive than other competitors and does not require a license.
What other advice do I have?
I recommend this solution to others who use the AWS cloud.
I rate Amazon EKS a ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Buyer's Guide
Download our free Amazon EKS Report and get advice and tips from experienced pros
sharing their opinions.
Updated: April 2025
Popular Comparisons
VMware Tanzu Platform
Red Hat OpenShift Container Platform
Rancher Labs
Kubernetes
Nutanix Kubernetes Engine NKE
Docker
HashiCorp Nomad
Komodor
HPE Ezmeral Container Platform
NGINX Ingress Controller
Buyer's Guide
Download our free Amazon EKS Report and get advice and tips from experienced pros
sharing their opinions.