Amazon EKS Reviews

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. 

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.

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.

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.

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.

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.

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.

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.

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.

Neutral

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.

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.

The product's initial setup phase was taken care of by one of our company's in-house teams.

I rate the overall product a seven 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.

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.

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. 

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. 

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.

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.

I rate the tool's stability a nine out of ten. 

The solution is very scalable. We have two customers for Amazon EKS. 

We don't use support. Our customers use it. 

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.

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.

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.