Amazon EKS Reviews

We run all our microservices across the globe with Amazon EKS. We also use it for development, testing, and maintenance.

In the past, we have faced challenges with scalability and maintenance while running clusters. Amazon EKS is very easy to maintain. So it allows us to focus on our deployment.

The most important aspect of Amazon EKS is that it is easy to set up and very easy to upgrade. So we can focus on maintaining and deploying our microservice. It is also easy to scale and easy to monitor.

Amazon EKS provides very minimum information during the upgrade of the node group. When the upgrade doesn't work well, it doesn't give enough information for us to troubleshoot. So it would be great if Amazon EKS provided more information in such cases. 

Amazon EKS should enable some AIOps.

I have been using Amazon EKS for the past three years.

As a Kubernetes-managed platform, it is pretty stable. You can stabilize the new version when it is available in AWS.

It is easy to set up, and the Amazon EKS control plane accommodates scaling.

Whenever we experience any challenges, we always get a very fast response from AWS support. We are happy with the support provided so far.

We shifted to Amazon EKS because we faced some issues with our old system on OpenShift. OpenShift also has a high license price as compared to Amazon EKS.

We had some challenges at the beginning. It took us a few weeks to get one cluster up. Later, we improved our approach by using Terraform to manage it. Now, we can set up many clusters within one or two hours. We use around 60 clusters now.

We implemented it through our in-house team.

Amazon EKS is very cost-effective. I rate the pricing a ten on a scale of one to ten.

Other teams in the organization are trying to explore Google Kubernetes Engine. However, for our team, AWS is a lot easier. Our team might not move to other cloud providers because running Terraform is very useful for us.

In the internal cluster, we have four hundred people working with Amazon EKS. We have a lot of customers running billions of transactions. Overall, I rate Amazon EKS a nine out of ten.

Amazon EKS is basically a model provided by Amazon that allows you to create and deploy multiple microservices and manage containers. Once the Kubernetes is installed, we can directly create the container, set up ports, and set up new services. We currently have Java containers running.

We have more than 500 people using this solution. We are on version 21.

I like the scalability they're currently providing. Integration was very easy. It was a good experience. 

The connectivity could be better.

I have been using Amazon EKS for more than two years.

It's stable enough. We have had network connectivity issues twice. We weren't able to figure out what went wrong there, and it caused a problem initially. When we restarted it, it began working again.

The scalability is good.

We have called technical support a couple of times. We had an issue with integration with Lambda. But we took the help of AWS and it was resolved.

We have also used the IBM private cloud, but it wasn't user friendly.

Setup can take half an hour to an hour.

For deployment, our technical team was made up of 15 people.

My company paid for the license. 

I would rate this solution 8 out of 10.

I would definitely recommend this solution. It's a very good application, and the scalability is very good.

Our primary use case for Amazon EKS is for running production workloads. The microservices-based modules are broken down and then hosted using EKS.

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. 

For now I can't suggest any improvements or additional features, the features we currently use we are very happy with. 

We have been using Amazon EKS for 8-9 months.

The Kubernetes solution has been very stable for us, there are no issues to report on that aspect. 

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. 

We have found Amazon to be quite responsive. We have experienced some minor issues and the response time was good. 

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.

There is no up front licensing cost, as this is a cloud based solution you pay-as-you-go.

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. 

It's a great service because we can do a lot of things using it. It's easy to create clusters and services in pods there.

So, the main purpose is to create clusters and services and define some pods there.

We reduced the cost by using one cluster instead of using different services and different virtual machines in a client. So, Amazon EKS helped our organization reduce costs. 

This is the way we can create a cluster because we don't need to pay attention to the control plane. We only need to deploy the services in the worker nodes and configure some configurations, easy configurations, and the cluster is done to be published.

Basically, AWS provides all features that we have prepared.

There is room for improvement in stability. I faced some problems with the App. The problem is actually the app, with the different teams fixing it.

I have been using this solution for 18 months. I work on different projects. Basically, we create a structure and per clients, and we move to another project. So we did different projects for how long of the year.

We are currently using version 1.24, but we are migrating to the latest version, which is 1.28.70.

I would rate the stability an eight out of ten. I faced some problems with the App. The problem is actually the app with the different teams fixing it, but I would say the Kubernetes - it's ten. The service is ten. But if everything is considered, it's eight.

I would rate the scalability a ten out of ten. It is perfect. Moreover, more than one hundred users have access per hour. 

We use this solution every day. Thus, we use the solution to its maximum potential. 

We did the research for Azure, but all the structure and other resources were applied in AWS, so we kept it in the same provider.

We also used a local structure, but we're at a short time. And the infrastructure had already been done. I only need to support the application. It's full.

The thing that takes more time to be constructed with the code is minutes and hours to provide the EKS code, but with the structure is really fast.

Basically, it used the code. They used the TerraForm code because we work with ESA, and, basically, the most important part for us is the code.

We used the help of a third party, like, the partners of Amazon. 

We required four people for the deployment process. However, the maintenance depends on the number of clusters and resources. So, two people are enough for the maintenance of the solution. 

I would rate the pricing model a seven out of ten, where one is cheap and ten is very expensive.

It was rather expensive; compared to GCP and Azure, it's a little more expensive. The price can be a problem for small-sized businesses. 

There are no additional costs to the standard license. 

So I work as a DevOps engineer. But basically, using TerraForm or other tools like that, I never worked with another provider as Google and Microsoft. So, basically, I use AWS. 

Actually, there are a lot of reports that I use every day. So we use tools related to that, like load balancers, ECRs, and EKS— so different resource things.

It's a great service. Some services are more expensive compared to other providers. But in general, it's the best option for medium or large enterprises.

Overall, I would rate the solution a nine out of ten. 

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.

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.

The solution's graphical interface is not the best. It could be better in terms of enabling some integrations or managing the configuration.

I have been using Amazon EKS for one or two years.

I rate the solution’s stability ten out of ten.

Amazon EKS is good when it comes to scaling the cluster, adding, removing, or upgrading the nodes. Upgrading the machine's resources is easy.

Amazon EKS has a big community, and support is really good.

The solution's initial setup was easy.

If the deployment fails, you're still up and running. Scaling up or down can be done with zero downtime.

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.

We use Amazon EKS to build integration projects and manage the infrastructure.  

Amazon EKS is compatible with Kubernetes API. I can use the autoscaling feature to manage and scale up infrastructure. I can monitor the cluster as well.

I encountered problems with the product’s documentation. Additionally, the CPU consumes a lot of memory. EKS could be modular like GCP as well.

We have been using Amazon EKS for one year.

The initial setup is more straightforward if you use the console.

I rate Amazon EKS’s pricing a nine out of ten. It costs around $200 and is expensive for the Brazilian market.

I rate Amazon EKS a nine out of ten.

We have a service hosting platform, and we use Amazon EKS for hosting web services.

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. 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.

I have been using Amazon EKS for five years.

Amazon EKS has good stability.

Amazon EKS's scalability is very low. Quite a few people are using the solution in our organization.

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.

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.

We have seen a return on investment with Amazon EKS.

Amazon EKS’s pricing is ok compared to its competitors.

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.

I only use it to define multi-tenants and define infrastructure.

Our company has around ten people using Amazon EKS off-site and on-site.

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.

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.

I have been working with Amazon EKS for two years now, and mainly use the Command Line Interface (CLI) version.

It is a stable solution.

It is a scalable solution for our services.

The response time of customer service and support is quick.

Positive

The initial setup is easy. I had some errors initially, but they were easy to terminate.

Our in-house team deployed it. It only took three days to set up and run a big infrastructure.

I would like a cheaper version of it.

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.