I used Amazon EKS for my personal learning purposes. I used the solution to learn how to initiate and upgrade the Kubernetes cluster for testing in my own lab.
Senior System Engineer at Techline-eg
Provides good performance and used for testing and learning purposes
Pros and Cons
- "The solution's performance is good."
- "The solution's graphical interface is not the best."
What is our primary use case?
What is most valuable?
Amazon EKS is a good tool for my testing and learning purposes. The solution's performance is good. It is a good solution for my learning and my labs.
What needs improvement?
The solution's graphical interface is not the best. It could be better in terms of enabling some integrations or managing the configuration.
For how long have I used the solution?
I have been using Amazon EKS for one or two years.
Buyer's Guide
Amazon EKS
February 2025
![PeerSpot Buyer's Guide](https://www.peerspot.com/images/peerspot_logo_lt.png)
Learn what your peers think about Amazon EKS. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
837,501 professionals have used our research since 2012.
What do I think about the stability of the solution?
I rate the solution’s stability ten out of ten.
What do I think about the scalability of the solution?
Amazon EKS is good when it comes to scaling the cluster, adding, removing, or upgrading the nodes. Upgrading the machine's resources is easy.
How are customer service and support?
Amazon EKS has a big community, and support is really good.
How was the initial setup?
The solution's initial setup was easy.
What was our ROI?
If the deployment fails, you're still up and running. Scaling up or down can be done with zero downtime.
What other advice do I have?
Some of the Kubernetes clusters were on Amazon, GCP, and Azure. I used most of them on-premises. I installed the Kubernetes cluster in my own environment.
Overall, I rate the solution ten out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Aug 11, 2024
Flag as inappropriate![PeerSpot user](https://www.peerspot.com/assets/media/images/anonymous_avatar-ddad8308.png)
Devops Engineer at Altimetrik (Deployed at FORD)
Though a great tool that supports autoscaling, it needs to consider improvements in its initial setup phase
Pros and Cons
- "The stability of the solution is good."
- "Amazon EKS is not a solution that can be fully managed through automation, making it an area of concern where improvement is required."
What is our primary use case?
The solution can be described as a microservice, and it is also a fully containerized platform. The solution can be described as a stateless service. Amazon EKS can be a great solution for deployments since it supports autoscaling and keeps scaling as well. In my company, we only pay for the resources we use, and owing to such a concept, we use the solution in our company.
What is most valuable?
The most valuable feature of the solution stems from the fact that it allows developers to shift applications. The value of the solution is good when compared to tools deployed on an on-premises model.
What needs improvement?
If you compare Amazon EKS with OpenShift, the latter provides users with a solution that is fully managed through automation. Amazon EKS is not a solution that can be fully managed through automation, making it an area of concern where improvement is required. Amazon EKS should be manageable through a web portal or web interface, a feature that exists in OpenShift.
Amazon EKS should be available as a fully managed service since we use Helm chart to deploy the product in our company right now.
The initial setup phase of the product is an area where certain improvements can be made.
For how long have I used the solution?
As a consultant, I use Amazon EKS, depending on the project requirements of my company. I have used Amazon EKS within the past twelve months. I am a customer of Amazon.
What do I think about the stability of the solution?
The stability of the solution is good. I can't comment much on the stability part of the solution since there is a different team in my company that takes care of the maintenance part of the solution.
What do I think about the scalability of the solution?
I won't be able to comment on the scalability of the solution. I haven't had any reasons to deal with the product's scalability options.
How are customer service and support?
I did not meet with any issues when trying to connect with the solution's technical support. At times, there may be some delays in response from the technical support team. I rate the technical support a seven out of ten.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
In the past, I was using another solution. I switched to Amazon from a different solution. Amazon's support is good. Amazon also provides a number of managed services.
How was the initial setup?
I rate the initial setup phase of the product a six on a scale of one to ten, where one is difficult, and ten is easy.
The initial setup phase of the product was a bit difficult.
The solution is deployed on Jenkins and CI/CD.
What about the implementation team?
The product's initial setup phase was taken care of by one of our company's in-house teams.
What other advice do I have?
I rate the overall product a seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Amazon EKS
February 2025
![PeerSpot Buyer's Guide](https://www.peerspot.com/images/peerspot_logo_lt.png)
Learn what your peers think about Amazon EKS. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
837,501 professionals have used our research since 2012.
Technical Architect at Kyanon Digital
Auto-scales efficiently and is good for mapping user content
Pros and Cons
- "I like its auto-scale feature very much."
- "The overall stability of the product should be improved to prevent any loss of data."
What is our primary use case?
I only use it to define multi-tenants and define infrastructure.
How has it helped my organization?
Our company has around ten people using Amazon EKS off-site and on-site.
What is most valuable?
I like its auto-scale feature very much. Moreover, it is easy to determine my course of action with many features available on EKS. However, I do have some concerns with Microsoft Edge. Overall, I find EKS to be a valuable solution.
What needs improvement?
The managed services of Amazon EKS could be improved. The system should have a closed-loop feedback mechanism to address any issues that users may face.
Moreover, the overall stability of the product should be improved to prevent any loss of data.
For how long have I used the solution?
I have been working with Amazon EKS for two years now, and mainly use the Command Line Interface (CLI) version.
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?
It is a scalable solution for our services.
How are customer service and support?
The response time of customer service and support is quick.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is easy. I had some errors initially, but they were easy to terminate.
What about the implementation team?
Our in-house team deployed it. It only took three days to set up and run a big infrastructure.
What's my experience with pricing, setup cost, and licensing?
I would like a cheaper version of it.
What other advice do I have?
Amazon EKS is good for managing and providing various services, and for using and mapping user content.
I would rate it a nine on a scale of one to ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Industry Principal at a tech services company with 10,001+ employees
Good auto scaling and service discovery abilities
Pros and Cons
- "The most valuable features of Amazon EKS are its auto scaling ability and the ability for service discovery."
- "Amazon EKS's vulnerability management of data could be improved."
What is our primary use case?
We have a service hosting platform, and we use Amazon EKS for hosting web services.
What is most valuable?
The most valuable features of Amazon EKS are its auto scaling ability and the ability for service discovery.
What needs improvement?
Amazon EKS's vulnerability management of data could be improved. Also, concerning vulnerability and version upgrades, many more things could be pulled into the control plane rather than keeping it in the data plane and having the users figure out how to upgrade their portions.
For how long have I used the solution?
I have been using Amazon EKS for five years.
What do I think about the stability of the solution?
Amazon EKS has good stability.
What do I think about the scalability of the solution?
Amazon EKS's scalability is very low. Quite a few people are using the solution in our organization.
How are customer service and support?
We had no issues contacting Amazon EKS's technical support and usually got the necessary support. However, as with any Kubernetes installation, only the control plane is covered by Amazon, not the data plane. So if there are issues on the data plane side, Amazon cannot be of much help.
How was the initial setup?
Amazon EKS’s initial setup was moderately easy. Amazon EKS's deployment was fast. We took the help of an automated deployment system, and the deployment was done in a couple of minutes.
What was our ROI?
We have seen a return on investment with Amazon EKS.
What's my experience with pricing, setup cost, and licensing?
Amazon EKS’s pricing is ok compared to its competitors.
What other advice do I have?
Amazon EKS is a good platform to use, but scale up before you start deploying in industrial quantities.
Overall, I 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.
CTO at BE1 consultancy
Provides high performance and easy manageability
Pros and Cons
- "Provides high performance and easy manageability."
- "The dashboard needs to be more user-friendly."
What is our primary use case?
We are using EKS for crypto exchange.
What is most valuable?
We chose this solution because with crypto exchange you need high performance and easy manageability. It offers highly available architecture, and with two or three Linux servers it distributes all containers through the Linux systems. If that's what you're looking for, it's a really good solution. It also allows for integrating their infrastructure as service capabilities.
What needs improvement?
The only important thing that needs to be improved is the EKS dashboard. It could be more user-friendly.
For how long have I used the solution?
We've been using this solution for about six months.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The solution is very scalable.
How are customer service and support?
We're very happy with the customer support.
How was the initial setup?
The initial setup was average in terms of complexity. We have one very good system admin person in our company, he has a lot of experience and carried out the deployment. We are still in a testing environment, so there are only around 15 users. We have around a million users and eventually they'll all be using it.
What's my experience with pricing, setup cost, and licensing?
We pay a monthly licensing fee which is quite high but they do provide good service.
What other advice do I have?
I rate this solution eight out of 10.
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.
Director - DevOps and Infrastructure at INTIGRAL
Improves application resiliency
Pros and Cons
- "Break down your application into small modules to improve resiliency"
What is our primary use case?
Our primary use case for Amazon EKS is for running production workloads. The microservices-based modules are broken down and then hosted using EKS.
What is most valuable?
The most valuable feature to us is orchestration when it comes to deploying. The main ideology behind Kubernetes is that you are breaking down your application into smaller modules. Instead of having a monolithic application, you make it a microservices-based module. Using an e-commerce website as an example, we would break down login's as a single module, registration as a single module and then in the event of an issue one does not impact the other.
With your small modules, in most cases, they share a backend, and that's how at the service layer you connect them by using an API gateway or a service mesh. This ensures scalability and they don't have any dependencies when it comes to failures. This means you can easily scale and optimize.
What needs improvement?
For now I can't suggest any improvements or additional features, the features we currently use we are very happy with.
For how long have I used the solution?
We have been using Amazon EKS for 8-9 months.
What do I think about the stability of the solution?
The Kubernetes solution has been very stable for us, there are no issues to report on that aspect.
What do I think about the scalability of the solution?
The beauty of Kubernetes is that you can scale it. You just have to define the workload and the scalability capability is managed itself. We just need to define the number of bots or services we want to run and it manages to scale up when needed.
How are customer service and support?
We have found Amazon to be quite responsive. We have experienced some minor issues and the response time was good.
How was the initial setup?
With regards to setup, you would need to have a basic understanding of Kubernetes and how it works before you start deploying your production workloads. Once we started working with Kubernetes and got hands-on experience there was not much hassle to roll out to production workloads.
What's my experience with pricing, setup cost, and licensing?
There is no up front licensing cost, as this is a cloud based solution you pay-as-you-go.
What other advice do I have?
The advice I would offer on Kubernetes is with the configuration of your applications. Some are compute-extensive, some are compute-optimized. If you don't configure this correctly it can lead to deadlocks. The compute power has to be enough when it comes to your applications. Some applications need more memory, for example, e-commerce sites need a good response time. In this example, you would want to configure a memory-based application.
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.
Solution architect at a tech services company with 51-200 employees
Offers horizontal and vertical scaling and useful for cloud-native applications
Pros and Cons
- "Amazon EKS is a useful solution for modern, cloud-native applications. It offers both horizontal and vertical scaling, which is a big advantage. The tool can also help manage costs while maintaining high availability."
- "The main thing to improve with Amazon EKS is the price. However, these services can be very expensive. For example, in countries like Turkey, the cost is too high. That's why we offer our cloud solutions locally. We developed hybrid solutions, but their prices are still very high."
What is our primary use case?
The use case for Amazon EKS is for a payment gateway corporation whose applications run on microservices. Their software team develops cloud-native applications. They use Amazon's public cloud for these applications but find it expensive. They want a less expensive solution for their customers.
We suggest using Amazon EKS open-source solutions. By using these solutions on-premises, they don't have to pay Amazon.
What is most valuable?
Amazon EKS is a useful solution for modern, cloud-native applications. It offers both horizontal and vertical scaling, which is a big advantage. The tool can also help manage costs while maintaining high availability.
Integrating Amazon EKS with other AWS services is easy if you know how to connect your applications and understand programming. It depends on how your application uses modern programming languages.
What needs improvement?
The main thing to improve with Amazon EKS is the price. However, these services can be very expensive. For example, in countries like Turkey, the cost is too high. That's why we offer our cloud solutions locally. We developed hybrid solutions, but their prices are still very high.
What do I think about the stability of the solution?
I rate the tool's stability a nine out of ten.
What do I think about the scalability of the solution?
The solution is very scalable. We have two customers for Amazon EKS.
How are customer service and support?
We don't use support. Our customers use it.
How was the initial setup?
The tool's deployment is easy. The deployment process is very simple. First, create an account. It's very organic. After that, choose the service that will be used for the project and create new services. Provide your credentials to connect to the environment. If you want to use a private link, you'll need to use a private connection.
What other advice do I have?
I rate the overall product a nine out of ten. If you want to start quickly and have time constraints, you can use Amazon solutions because no time or effort is needed to prepare your environment for the market, and no hardware or infrastructure requirements are required.
It can affect team productivity with a few customers. Productivity depends on the customers' knowledge. If their developers or software team are familiar with using hyperscale issues, it is very productive to use it.
If you need off-site backup solutions, object storage, or to check your data's secondary version for disaster recovery, you can use AWS Backup or Amazon EKS service, like S3 buckets. It's very useful.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Head of Digital Transformation at a computer software company with 1,001-5,000 employees
Great tool for complex environment with multiple applications
Pros and Cons
- "The product helps us to configure the new environment."
- "The tool's setup is complex."
What is our primary use case?
The product helps to create a new environment fast.
How has it helped my organization?
The tool helps us to provide greater access and also scale applications faster.
What is most valuable?
The product helps us to configure the new environment.
What needs improvement?
The tool's setup is complex.
For how long have I used the solution?
I have been working with the product for three years.
What do I think about the stability of the solution?
I would rate the product's stability a ten out of ten.
What do I think about the scalability of the solution?
I would rate the product's scalability a ten out of ten. My company has around 1000 users of the tool. We have plans to increase the usage in future.
How was the initial setup?
The tool's setup is difficult and requires experienced people.
What other advice do I have?
I would rate the tool a ten out of ten. The product is very easy to use since it is based on Kubernetes. It is a great tool for complex environments with multiple applications.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
![PeerSpot user](https://www.peerspot.com/assets/media/images/anonymous_avatar-ddad8308.png)
Buyer's Guide
Download our free Amazon EKS Report and get advice and tips from experienced pros
sharing their opinions.
Updated: February 2025
Popular Comparisons
VMware Tanzu Platform
Red Hat OpenShift Container Platform
Rancher Labs
Kubernetes
Nutanix Kubernetes Engine NKE
Docker
HashiCorp Nomad
HPE Ezmeral Container Platform
Komodor
NGINX Ingress Controller
Buyer's Guide
Download our free Amazon EKS Report and get advice and tips from experienced pros
sharing their opinions.