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.

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's a great service because we can do a lot of things using it. It's easy to create clusters and services in pods there.

So, the main purpose is to create clusters and services and define some pods there.

We reduced the cost by using one cluster instead of using different services and different virtual machines in a client. So, Amazon EKS helped our organization reduce costs. 

This is the way we can create a cluster because we don't need to pay attention to the control plane. We only need to deploy the services in the worker nodes and configure some configurations, easy configurations, and the cluster is done to be published.

Basically, AWS provides all features that we have prepared.

There is room for improvement in stability. I faced some problems with the App. The problem is actually the app, with the different teams fixing it.

I have been using this solution for 18 months. I work on different projects. Basically, we create a structure and per clients, and we move to another project. So we did different projects for how long of the year.

We are currently using version 1.24, but we are migrating to the latest version, which is 1.28.70.

I would rate the stability an eight out of ten. I faced some problems with the App. The problem is actually the app with the different teams fixing it, but I would say the Kubernetes - it's ten. The service is ten. But if everything is considered, it's eight.

I would rate the scalability a ten out of ten. It is perfect. Moreover, more than one hundred users have access per hour. 

We use this solution every day. Thus, we use the solution to its maximum potential. 

We did the research for Azure, but all the structure and other resources were applied in AWS, so we kept it in the same provider.

We also used a local structure, but we're at a short time. And the infrastructure had already been done. I only need to support the application. It's full.

The thing that takes more time to be constructed with the code is minutes and hours to provide the EKS code, but with the structure is really fast.

Basically, it used the code. They used the TerraForm code because we work with ESA, and, basically, the most important part for us is the code.

We used the help of a third party, like, the partners of Amazon. 

We required four people for the deployment process. However, the maintenance depends on the number of clusters and resources. So, two people are enough for the maintenance of the solution. 

I would rate the pricing model a seven out of ten, where one is cheap and ten is very expensive.

It was rather expensive; compared to GCP and Azure, it's a little more expensive. The price can be a problem for small-sized businesses. 

There are no additional costs to the standard license. 

So I work as a DevOps engineer. But basically, using TerraForm or other tools like that, I never worked with another provider as Google and Microsoft. So, basically, I use AWS. 

Actually, there are a lot of reports that I use every day. So we use tools related to that, like load balancers, ECRs, and EKS— so different resource things.

It's a great service. Some services are more expensive compared to other providers. But in general, it's the best option for medium or large enterprises.

Overall, I would rate the solution a nine out of ten. 

Amazon EKS is like Kubernetes, but it helps manage our nodes and scalability in AWS.

Amazon EKS should improve its integration. Our company does not maintain the external infrastructure.

Amazon EKS should include a graphic interface. Like there is a dashboard in Kubernetes, Amazon EKS should have a graphic interface that is more fluid, more fluent and contains more information.

I have been using Amazon EKS for six months.

Amazon EKS is a very stable solution.

I rate Amazon EKS a nine out of ten for stability.

Amazon EKS has high scalability. The solution has 10 to 15 endpoints in our organization. The solution is used 24/7 in our organization.

I rate Amazon EKS a nine out of ten for scalability.

Before Amazon EKS, I previously used OpenShift and Kubernetes-native.

The solution's initial setup depends on the application inside it. It's easy to have Kubernetes, but deploying other solutions with EKS is hard. It is easy to deploy Amazon EKS in general. I rate the solution an eight out of ten for the ease of its setup.

It took us half a day to deploy Amazon EKS. The solution's deployment depends on whether you want to use the Terraform ECR infrastructure. You have to go to the panel in AWS and deploy Amazon EKS. We needed an integrator for the first time, but then we did everything ourselves for the next deployments. Only one person is required for the deployment and maintenance of the solution.

Amazon EKS is quite pricey, but the functionality it provides is worth it. The solution has no additional costs, but it depends on the number of nodes used inside it. If we have a lot of traffic, we should scale many nodes, which would cost a lot.

On a scale of one to ten, where one is cheap, and ten is expensive, I rate the solution's pricing an eight out of ten.

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

The main use case is Cloud and IT applications.

It's a faster solution to adopt on native applications.

I would like to see a cloud setup bank management feature.

I have been using Amazon EKS for six years.

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

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

There is a return on investment.

Before EKS, we evaluated AKS and CKS.

Review the organization's strategy with your strategy, whether it is oriented to the portability of your applications. Overall, I would rate Amazon EKS a nine out of ten.

We deploy different solutions on the EKS cluster for our clients to use.

Since it is a managed service of AWS, Amazon EKS helps us in the managing and autoscaling of services. We don't have to worry about multiple things like managing the nodes or IP addresses and can focus on our work.

Through Amazon EKS, we can have the blue-green deployment very easily.

The management of the nodes in Amazon EKS should be improved. AWS should reduce the constant upgrades of the nodes of Amazon EKS or EC2 machines.

I have been using Amazon EKS for almost two years.

I rate Amazon EKS a seven out of ten for stability.

I rate Amazon EKS a nine out of ten for scalability.

The solution's technical support is very good.

Positive

The solution's initial setup is straightforward for us because we use Terraform scripts, which we have written and can reuse. It is the same for the console.

If your application goes to production, you will definitely see an ROI with Amazon EKS.

The solution's pricing is fair enough and a little less costly.

I would recommend Amazon EKS to other users.

Overall, I rate Amazon EKS an eight out of ten.

I use EKS as an application management system and a second application server. It's connected to Amazon RDS. 

EKS has security features that you can't find in competing solutions.

I'm having difficulty getting my AWS clusters to communicate with my local machine. 

I have used EKS for three years.

Amazon EKS is scalable. We have about 20,000 users. 

Setting up EKS is simple compared to OpenShift. It isn't too complex. We have a hybrid setup due to government data rules. I deployed EKS alone.

I rate EKS seven out of 10 for affordability. Amazon EKS costs us $730 a year. 

I rate Amazon EKS nine out of 10.

I have clients that run on Kubernetes engines. 

The tool works well with the nodes in AWS. It's scalability is also good in terms of architecture. 

I am not impressed with the tool's Amazon console. It also needs to add security features. 

I have been working with the product for four years. 

I would rate the solution's stability a ten out of ten. 

I would rate the product's scalability a ten out of ten. 

The tool's premium support is good. 

Positive

The solution's deployment gets completed in minutes. You need one DevOps engineer to maintain the solution. 

The solution is pricey. The tool's pricing is monthly. 

I would rate the solution a ten out of ten. It is the best platform for Kubernetes. The tool is also compliant. You need a demo to get started with it. 

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.