Amazon EKS Reviews

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.

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 mainly use EKS for containers. We use Kubernetes for scalable deployments.

We're using EKS because our customers requested it. They wanted autoscaling functionality. We have our own product, and we deploy it for our customers in Amazon cloud.

The containers are built, registered, and then kept in a repository at the docker site. Our IT department has an account there. From there, it's exposed and we use the Amazon template surveys and cloud formation template. Then, our IT team creates CFTs. The scripts are run, and the containers are deployed from there.

It's a hybrid solution.

EKS provides autoscaling functionality.

I started using EKS about eight months ago.

It's reasonably stable. EKS is used with Fargate.

From what I understand, it's scalable. I haven't heard of any issues.

Setup depends on what kind of architecture you have.

It depends on the script that's prepared. Once the script is done, just one person is needed for deployment.

We have an internal team that takes care of deployment. They're a specialized team.

I would rate this solution as eight out of ten.

My advice is that not every architecture can fit into EKS. You have to really evaluate whether EKS is suitable for the kind of design and architecture you have. Evaluate it first and then attempt 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. 

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