Amazon EKS Reviews

Our primary use case is related to our ecommerce solution, which is very high in terms of data in the database and products. It has one hundred thousand first line items. We developed a system connected with AWS services to translate search keywords into different languages and improve search results accuracy on our ecommerce site.

The scalability has really helped us a lot in enhancing the customer experience and ensuring quick results. The ROI is really good, especially when compared with other services on-premises.

Amazon EKS provides good support. The integration and stability are clear and reliable. The scalability is excellent, allowing us to efficiently handle customer experiences and improve operational efficiency.

Sometimes, we face minor connectivity issues. However, it depends on the applications we are using. Improvement might be needed based on different use cases.

We have been using it since 2015.

The stability of Amazon EKS is clear and reliable.

Amazon EKS's scalability is clear and has improved our operational efficiency a lot.

The customer service and support are good, and we have a paid subscription that provides priority support.

The initial setup was handled by third parties. It involved some complexities, and appropriate inputs were necessary.

We worked with a third-party team for implementation, including many developers.

We did several ROIs, which showed positive results. It's particularly beneficial compared to investing in hardware.

The licensing cost is acceptable.

Before implementing, ensure thorough research and ROI analysis. The implementation should be handled by experienced personnel.

I'd rate the solution eight out of ten.

I am working mostly on AWS infrastructure services, such as EC2, EKS, RDS, CloudFormation, IAM, and CloudWatch. I have around one year of experience with Kubernetes and have been using AWS services continuously for three years. My responsibilities include working on server storage, containerization, monitoring, and access policies.

Simplifies Kubernetes setup and management.AWS handles cluster upgrades, patches, and availability.Seamlessly integrates with AWS services like IAM, CloudWatch, and VPC.Access to advanced networking, security, and monitoring tools.EKS automatically deploys the Kubernetes control plane across multiple AWS Availability Zones for fault tolerance.

I have around one year of experience using Kubernetes with AWS.

In my project, AWS EKS has shown stability without any issues.

EKS offers excellent scalability, especially compared to Docker Swarm. The ability to scale based on requirements by deploying additional containers is a strong point for Kubernetes.

I have not contacted technical support regarding EKS.

Positive

I have explored Google Kubernetes Service in my personal projects but did not work on any other Kubernetes projects before EKS.

The initial setup is relatively straightforward when using the AWS Management Console. Setting up clusters and nodes is simplified through AWS's interface compared to on-premises. It took approximately 15 to 20 minutes to complete the setup.

I do not have specific details on EKS's pricing and licensing compared to other services. However, in general, deploying in the cloud offers lower latency and high availability and reduces manual intervention and responsibility, leading to some operational efficiencies.

I have worked with Google Kubernetes Service in my personal space but have not evaluated others for professional use.

For large-scale enterprise solutions, Kubernetes is recommended due to its scalability. Despite costing considerations, EKS alleviates the burden of procedural complexities, making it suitable for enterprise-level applications.

I'd rate the solution eight out of ten.

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.

Amazon EKS is used as a container orchestration platform. Customers use it to develop applications which are containerized and need to be deployed. Kubernetes is the most popular platform across the industry.

Amazon EKS offers replatforming and migration capabilities to our customers, enabling them to move from AWS to other platforms like AKS with minimal changes. It has also helped in smooth integration with other AWS services, especially API gateways and databases.

The serverless capability of Amazon EKS is quite valuable. Earlier, it was necessary to know the exact configuration, including the number of pods and nodes. Now, with the serverless option, you can deploy everything and AWS handles the infrastructure.

Amazon EKS could improve in its pricing model, particularly for medium-sized customers who might find the support costs high.

I have used Amazon EKS for the past five to six years.

I rate the stability of Amazon EKS as ten out of ten. It is highly stable.

Amazon EKS has high scalability. It can scale very well according to needs, and it doesn't have any issues with scalability.

Amazon's technical support is quite good, especially for those who purchase support services. As a partner, we receive excellent support due to our relationship with Amazon.

Positive

The initial setup of Amazon EKS is much less complex compared to setting up Kubernetes manually on Linux virtual machines, as it takes away the complexities of installing and configuring everything.

We have experience working with both EKS from AWS and AKS from Microsoft Azure, as well as Google GKE.

For those who are Amazon customers and want to deploy containerized applications, Amazon EKS is the best option.

I'd rate the solution ten out of ten.

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.

Amazon EKS is like Kubernetes, but it helps manage our nodes and scalability in AWS.

Amazon EKS should improve its integration. Our company does not maintain the external infrastructure.

Amazon EKS should include a graphic interface. Like there is a dashboard in Kubernetes, Amazon EKS should have a graphic interface that is more fluid, more fluent and contains more information.

I have been using Amazon EKS for six months.

Amazon EKS is a very stable solution.

I rate Amazon EKS a nine out of ten for stability.

Amazon EKS has high scalability. The solution has 10 to 15 endpoints in our organization. The solution is used 24/7 in our organization.

I rate Amazon EKS a nine out of ten for scalability.

Before Amazon EKS, I previously used OpenShift and Kubernetes-native.

The solution's initial setup depends on the application inside it. It's easy to have Kubernetes, but deploying other solutions with EKS is hard. It is easy to deploy Amazon EKS in general. I rate the solution an eight out of ten for the ease of its setup.

It took us half a day to deploy Amazon EKS. The solution's deployment depends on whether you want to use the Terraform ECR infrastructure. You have to go to the panel in AWS and deploy Amazon EKS. We needed an integrator for the first time, but then we did everything ourselves for the next deployments. Only one person is required for the deployment and maintenance of the solution.

Amazon EKS is quite pricey, but the functionality it provides is worth it. The solution has no additional costs, but it depends on the number of nodes used inside it. If we have a lot of traffic, we should scale many nodes, which would cost a lot.

On a scale of one to ten, where one is cheap, and ten is expensive, I rate the solution's pricing an eight out of ten.

Overall, I rate Amazon EKS a nine out of ten.

We use Amazon EKS to manage containerization within our microservices environment.

The product's most valuable features are scalability, observability, and performance.

They could add logging features. At present, we use external tools to increase and decrease the number of instances.

We have been using Amazon EKS for three years.

It is a stable service. We never encountered system downtime.

In organizational environments, especially when utilizing the console, EKS is the primary choice. Out of ten clients, approximately eight opt for EKS due to its scalability and robust features.

We contacted AWS support for EKS when we encountered difficulties connecting to private subnets. The support team guided us through the necessary steps to address these issues.

Scalability and security considerations drove the decision to migrate to EKS from another product.

The initial setup was straightforward, especially when Terraform was utilized to generate the setup. We must make minor adjustments, such as changing the name and configuring VPN settings. Overall, it's a relatively easy task for me.

The platform is worth the investment.

The product pricing depends on the specific requirements. For instance, clients between $3000-$4000 per month might find the pricing reasonable, with clusters priced around $70 to $80 plus additional costs. However, the actual pricing can vary based on the number of services utilized.

With numerous tools and plugins available for EKS like Graphite and Prometheus, users can effectively manage logs and monitor performance.

For beginners, it's essential to grasp the fundamentals of Docker and containerization and understand how containers operate. Once these basics are clear, the next step is to familiarize oneself with Kubernetes and container orchestration concepts.

I rate it a nine out of ten.

Amazon EKS can be used to implement and create clusters. It is also used to deploy and secure the already configured applications. EKS is a cloud-based container management service that integrates with Kubernetes to deploy applications. It automatically manages and scales clusters of infrastructure resources on AWS with Kubernetes.

EKS eliminates the need to install, operate, or maintain a Kubernetes control plane on AWS. Amazon handles everything. We just need to know how we can make it more secure, and we can use it to deploy your applications. It scales automatically, making it one of the best services.

Assigning roles and responsibilities to interact with a created cluster as a user over a command prompt is cumbersome on AWS. Initially, we create a user to interact with a cluster. Since everyone can't use the cluster, we need to assign some permissions to that specific user. It is very cumbersome to assign permissions to users to interact with a cluster. We always get errors, and it takes many days to resolve that permission issue before the user can start interacting with the cluster.

I have been using Amazon EKS for eight years.

Amazon EKS is a stable solution.

Amazon EKS is a scalable solution.

The solution’s technical support is good.

The solution’s initial setup is easy, but assigning permissions to users is difficult.

Amazon EKS is not a cheap solution.

Google Cloud Platform has a service similar to EKS called GKE. It's very easy to implement permissions in GKE as compared to EKS.

Overall, I rate Amazon EKS a seven out of ten.

We use EKS in our company to run containerized applications. I work in the container ecosystem team, and we manage EKS clusters for our developer teams so they don't have to. We provide them with the necessary tools to run on top of the cluster.

EKS helps us simplify and speed up cluster management. We don't have to take care of cluster updates; we just initiate the update, and AWS handles it. The same goes for some of the AWS-managed add-ons.

The biggest improvement is that we now have more time. When we shifted the responsibility of cluster management and updates to AWS, we had more time to develop solutions that make life easier for the developers. 

Application deployment is more automatic. They don't have to issue cluster commands; they can simply do a commit into our internal GitHub Enterprise, and our tooling will deploy or update the application on the cluster. That's probably the biggest benefit because we had time to develop such solutions.

From my personal perspective, I think it's good that we can use AWS CLI to manage the cluster, and that way, we can automate the work via scripts. Of course, the way that we just issue a command and AWS handles the work, like with cluster updates, is also valuable. That's probably one of the reasons why we use it.

Sometimes I have trouble because, in our corporate network, there are various networks, etcetera. It's difficult to connect to some of the clusters, and it's easier to go through the UI when troubleshooting something. At some points, the UI seems limited to me with the functions it provides. 

You can get information like what kind of port is running on the cluster, but I haven't really explored the UI so far, so it's difficult for me to see the logs, for example. Or sometimes, you are only limited to the basic Kubernetes things. 

We have certain customizations installed in the cluster, and for that, you really have to use kubectl from the command line. You are not able to use the EKS UI to list certain custom resources. So maybe there can be some kind of improvement, but maybe it's just me that I haven't really explored the UI that much.

I have been using it since February. 

I don't really remember any issue with EKS, the product from AWS as is. There can be some issues when there is a bigger outage on the AWS side; it's either some kind of network outage when we cannot reach AWS itself or something similar, but I wouldn't blame EKS for it.

When we had problems with the cluster itself, I think it was more about some issue that either we as a team introduced by human error, from some configuration mistake, or our customers sometimes made mistakes. And maybe there are issues when the application running on top of EKS somehow gets into some loop or something and then doesn't work correctly, but I wouldn't really attribute that to EKS.

Because I've been in the team for a short amount of time, I don't really remember any big issue that was caused by EKS itself in the past six months at least.

It is scalable. We use the cluster autoscaler tool that spins up a new node when we need more, and that works nicely. So I think from the scalability point of view, it's okay. 

In the last six months, I don't really see any issue with scalability. We run around one hundred clusters. Some of them are quite small, really just the basics where we are running free master nodes in the free availability zones, just to make things according to best practices. So, really a minimal cluster. 

And there are also some really big clusters with over a hundred worker nodes. Overall, I think it's quite big. And with EKS, we are able to manage it quite well.

I have some experience with AWS support, and it was good. We were trying to solve something with one of the add-ons, and I think we solved it within a couple of days. We even had a call with one of the support engineers. So I think it worked out well. 

The issue was regarding one of the AWS-managed add-ons. I remember that we clearly had some kind of misunderstanding between us and technical support, and it seemed like either we were not able to explain it correctly or the guy wasn't able to understand us. But I remember that somehow we solved that issue. So at the end, it was okay.

Neutral

The deployment process of EKS was done before I joined the team.

For me, EKS UI is nice, and it was quite easy for me to get familiar with. I find the AWS CLI quite nice to use as well. I've been working in IT for some time now, so I have some level of experience. I guess these things come sort of naturally to me now, such as how to use the tools that are provided by companies. It's usually no issue for me.

From the maintenance point of view, I don't know much about how things are backed up, etcetera. I think that is exactly why we use EKS because we don't really have to take care of cluster backups. We can simply issue a command, and the cluster will update. If we were to do cluster updates manually, it would be more work. We would have to update the worker nodes and then update the master node one by one. AWS now handles all of this. So I think from the maintenance point of view, it's great, and that's why we use it because it's now much more simple and faster for us.

We still see the benefits of using this solution because we are using it. And we actually plan to transfer all our workloads to EKS if things were ideal. But for some legal reasons, we still have to manage some on-premise clusters, but I think the benefits are there.

If you have the money, I would recommend the EKS product to other users who are looking into implementing it. It's a good tool. It really takes some of the management burden off your back.

Overall, I would rate it an eight out of ten. 

We deploy different solutions on the EKS cluster for our clients to use.

Since it is a managed service of AWS, Amazon EKS helps us in the managing and autoscaling of services. We don't have to worry about multiple things like managing the nodes or IP addresses and can focus on our work.

Through Amazon EKS, we can have the blue-green deployment very easily.

The management of the nodes in Amazon EKS should be improved. AWS should reduce the constant upgrades of the nodes of Amazon EKS or EC2 machines.

I have been using Amazon EKS for almost two years.

I rate Amazon EKS a seven out of ten for stability.

I rate Amazon EKS a nine out of ten for scalability.

The solution's technical support is very good.

Positive

The solution's initial setup is straightforward for us because we use Terraform scripts, which we have written and can reuse. It is the same for the console.

If your application goes to production, you will definitely see an ROI with Amazon EKS.

The solution's pricing is fair enough and a little less costly.

I would recommend Amazon EKS to other users.

Overall, I rate Amazon EKS an eight out of ten.