Amazon EKS Reviews

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.

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.

Our primary use case is for distribution computing.

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.

I have been using Amazon EKS for the past six months.

The current stability is very good.

There is sufficient scalability.

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.

The initial setup is quite straightforward.

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.

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. 

It's mainly deployed on a public cloud.

The graphical user interface could be better.

I have used Amazon EKS for three years.

I would rate the stability as eight out of ten.

I would rate the scalability as eight out of ten.

I would rate technical support as eight out of ten.

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.

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.

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.

I would rate this solution as eight out of ten. 

I highly recommend Amazon EKS.

Our main use case is when our client or the customer would like to have their service on AWS. When the client preference is AWS.

Our company prefers Amazon EKS to ECS.

The feature that I have found most valuable is that it is very user-friendly.

I would like to see it a little more stable, more operational, and more convenient to develop.

I have been using Amazon EKS for about two to three years.

Amazon EKS is very stable.

We have about 500 people in our organization using it.

Our technical team for the deployment and maintenance is only five people, one manager and four engineers.

We are definitely going to continue using this solution.

For container management, I had been using the IBM SP solution, but frankly speaking I don't like the IBM Cloud.

The initial installation was straightforward. It took under 30 minutes.

I love dealing with EKS. Personally, I like to deal with the Kubernetes solution.

On a scale of one to the, I would rate EKS a nine.

I would recommend Amazon EKS to others.

We use Amazon EKS for our proprietary solutions and applications. 

Amazon EKS is very scalable. 

Amazon EKS needs to improve customer operations and technical support. 

I have been working with the tool for five years. 

The tool's stability is high. 

We don't need technical support at the moment. 

The tool's deployment is not complex. 

Amazon EKS is a good investment. 

The tool's pricing is good. 

I would rate Amazon EKS an eight out of ten.