Amazon EKS Reviews

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.

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. 

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

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.

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.

Amazon Elastic Kubernetes Service (EKS) solution integrates AWS cloud with Kubernetes. Kubernetes is an open-source container technology that is popular right now. It has the ability to replicate applications for scaling.

Having this solution on the cloud has allowed us to focus more on our business because we do not have to worry about our own infrastructure.

We do not have to do a lot of administration, such as create virtual machines, or worry about our controllers or nodes going down because the solution is fully managed by Amazon.

You are able to have your applications on the cluster which provides the ability to replicate and scale them.

I have been using the solution for approximately two years.

The solution is stable.

I have found the solution scalable. 

This solution is used by the three-person DevOps team in my organization.

The technical support is very good.

The creation of the clusters only takes approximately 10 minutes.

We did the installation and configuration ourselves.

The solution is more expensive than other competitors and does not require a license.

I recommend this solution to others who use the AWS cloud.

I rate Amazon EKS a ten out of ten.

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.