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. 

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.

I have tried to host the enterprise content management application of IBM FileNet on Amazon EKS. That's the main use case. 

The solution has very good basic features.

The provisioning is very good we use it for the containerization of COTS applications.

The product is stable. 

If a company needs to scale the solution, it can.

The initial setup is simple. 

We've found the solution's technical support to be helpful and responsive.

There isn't something that is unique or outstanding. 

I'd like to see the solution add a service catalog.

I've used the solution for quite a number of years. It's been around three so far. 

We've found the solution to be stable. Currently, it's used on standard VMs. If we put it on Kubernetes clusters, it is highly reliable as well as easy to monitor, manage, and operate. It's great.

The solution is absolutely scalable. There are many enterprises running their businesses on this.

I'm not deploying anything for customers or a certain number of users. I'm just doing it for my own purposes. I'm learning about it and I'm trying new things. I propose these ideas to customers for various solutions and the implementations are done by another team, the delivery team, later. I can't speak to how many people ultimately end up using it.

Technical support is very good. There is no issue. There's no delayed response for their support. There's no lack of support. They are very helpful and we are quite satisfied. 

The initial setup is not overly complex or difficult. It's very simple, very straightforward. The instruction guides are all available and it's enough to get a user through the setup process. They are quite helpful guides. 

We have a professional services team that does the job day in, day out. That said, I do it for my learning and I practice something on my own too. Therefore, I am also very capable of handling the initial setup myself. 

We already have costs built into the service given by the particular vendor. If it is on-premise, we buy the software, and we pay some support costs and license costs. However, if it is on the cloud, it is a pay-per-use model. 

I'm an integrator of the solution. 

The solution can be deployed both on the cloud and on-premises. 

We are using the latest version of the solution at this time. I can't speak to the exact version number, however.

I would recommend this solution to others. 

I'd rate the product at a nine out of ten. We're pretty happy with its capabilities so far. 

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

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.