Amazon EKS Reviews

The product helps to create a new environment fast. 

The tool helps us to provide greater access and also scale applications faster.

The product helps us to configure the new environment. 

The tool's setup is complex. 

I have been working with the product for three years. 

I would rate the product's stability a ten out of ten.

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. 

The tool's setup is difficult and requires experienced people. 

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. 

We are using EKS for crypto exchange. 

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. 

The only important thing that needs to be improved is the EKS dashboard. It could be more user-friendly. 

We've been using this solution for about six months. 

The solution is stable. 

The solution is very scalable. 

We're very happy with the customer support. 

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. 

We pay a monthly licensing fee which is quite high but they do provide good service.

I rate this solution eight out of 10. 

Our primary case is using Amazon EKS with all of our data in our MapReduce, map clusters, and our data clusters. And from there, we just input the information using Python and do our analysis using that.

We have problems with setting up virtual environments and installing the right packages. I believe the initial setup could be a better experience and faster customer support.

I have been using Amazon EKS for the past one and half years now.

The stability is excellent.

The scalability is not a problem we currently have five to six thousand employees using Amazon EKS.

Technical support or customer support is good but could be faster.

For us in our company, it is a very straightforward process because they had built a layer that is very useful for the users with just a couple of clicks. But normally, if you ask me in person, I think it is a bit cumbersome.

It can be done in-house but they have to read a lot of documentation from the AWS provider in order for it to make sense.

When you compare it to on-premises it is much better because, with on-premise, we have to look into data security and all these items. Amazon EKS eliminates that and becomes a cost-benefit for us.

On a scale of one to ten, I would give it a six. With the correct technical support individual, you can do well with implementation. If you are not sure about the technical support side for implementation I would wait until you are ready.

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.

It is challenging to host the applications in the existing VPC of the solution. They should include some essential configuration features to it.

We have been using the solution for the last two to three years.

It is a stable solution. I rate its stability as an eight or nine. Although, it is difficult to find a stable version sometimes.

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.

The solution's customer service is excellent. They also provide detailed documentation.

Positive

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.

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.

I rate the solution as an eight. I advise others to use EKS ETL instead of AWS command prompt while deploying it.

We just implemented the acquisition project for our cloud application environment, and we implemented Amazon EKS.

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.

They should improve the security and include some cloud-native project integrations. In addition, they should enhance the Jira integration.

We have been using this solution for about two years, and it is deployed on cloud.

It is a stable 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.

We have not needed technical support.

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.

It's a subscription and depends on the cluster nodes and other effects. There are many calculation criteria for licensing.

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.

I rate the solution a nine out of ten and recommend it to others.

Our client is doing some image analysis, and we need a robust system that won't go down during the image rotation, so we are using Amazon EKS. With this solution, our services will not go down during their work, and data will remain safe and available to the user.

Firstly, whenever a service goes down, EKS automatically makes up that part, enabling the services to remain available. And secondly, whenever we deploy anything, we don't have to consider security between services because EKS provides that as well. We need to configure some supportive plug-ins and tools, which is relatively easy. This feature also provides monitoring, so if our service goes down, we have an alert mechanism and logging.

We can deploy EKS microservices on any service we are developing.

The solution could be improved by adding monitoring, filtering, and logging capabilities to its current CloudWatch features.

We've been using the solution for one and a half years.

We haven't faced any major issues in one and a half years of use. We had an issue with storage, which we capped, giving us access to more space from the cloud. There are some other minor issues, but nothing major.

I would rate the solution's stability as eight out of 10.

We use the solution because it allows you to scale your application up and down. 

We have 500 data scientists actively using our EKS tool at any time.

We usually get support on time, but sometimes we have critical issues or something they need more time to deal with. 

We would give them nine out of 10 for the quality of support.

The initial setup is straightforward.

When deploying the solution, we used Jenkins to develop a CI/CD pipeline. It was a one-person job that took about 20 to 25 minutes.

On a scale of one to 10, we would give the product an overall rating of eight.

EKS is for deploying microservice projects. If you have multiple services in your application, you can deploy them and design your application accordingly.

We can deploy EKS microservices on any service we are developing.

I would certainly recommend the product to new users, but it would depend on the technology stack and the project. If a certain use case requires EKS, I would definitely advise using EKS rather than Google or Azure's EKS. I recommend Amazon Cloud Services for its reliable support and minimum downtime. 

We use Amazon Elastic Kubernetes Service (EKS) to manage our containers and to run and scale Kubernetes applications in the cloud.

Overall Amazon EKS is a good solution in the industry. The solution can support multi tendencies, and network isolations are the key factors.

Amazon EKS is predominately public. However, the government has started to have a lot of interest in Kubernetes and is receiving more education on Kubernetes and Amazon EKS. If we can have the security of Amazon EKS align with the security that is set out by the government it would be much better.

I have been using Amazon EKS for approximately six months.

Amazon EKS is scalable.

We are in the process of migrating from OpenShift to Amazon EKS which will be a lot of work to migrate over. We have about over 300 developers who are going to use Amazon EKS in the future.

We have previously used OpenShift.

I did the implementation of the solution myself in my organization.

I have found OpenShift to be a better tool and I would recommend it.

I rate Amazon EKS an eight out of ten.