Amazon EKS Reviews

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.

Amazon EKS is used in containerization, which means that you deploy any application and package it into its own miniature server. Then, store that application in an encapsulated form within a server which is an operating system, and keep it aside so that the repository recurses.

It has always helped me. It is the repository where we store our images.

It's a cluster service. So Amazon EKS is essentially a Kubernetes service, which is a product created by Google and is open-sourced, meaning it can be downloaded and installed on a server in a company's data center without needing the cloud for containerization or microservices. With Kubernetes, you can build and deploy microservice applications within a Kubernetes cluster. So, all your microservices will be running under Kubernetes within a cluster. Kubernetes is what that particular class of software is called, and we refer to it as an orchestration tool. It'll figure out and make sure that your microservice is always available. So, you can go and tell them before starting Kubernetes about the number of properties, files, or variables and issue commands to determine the instances of microservices available, including setting a minimum of one or two instances. To shut down a microservice, you can set the instances to zero. Essentially, Kubernetes allows an organization or anyone to have a cluster of microservices served without needing a cloud. Amazon AWS offers Kubernetes as a service because they found that many people are using Kubernetes.

The microservices appear to be well-made, and I don't have any comments on them as I don't see any flaws. Essentially, each microservice has a substantial ephemeral space available, providing gigabytes of storage. It would be helpful if this default storage allocation could be reduced to avoid the need for excessive resources when running microservices.

The goal and idea behind microservices are to always be available and capable of handling any load, no matter how many requests come through. At times, there might be millions of requests from people. All of these services are great, but I also think it would be useful to have the same technology available in a miniature resource size, enabling the same applications and services to run on a small machine. Increasing resources should enable microservices to handle the demands of the world. I would like to see the technology scale up to the point where individuals can run a service from home even with fewer resources.

I have been using Amazon EKS for about four years, and there is no specific version of the tool because it automatically gets updated. So, the latest version is always available.

I personally prefer this solution to Amazon Fargate and would rate it an eight out of ten.

The primary use case for Amazon EKS involves microservices and micro frontends.

The most valuable features of Amazon EKS are its scalability features.

There is room for improvement in the interface of Amazon EKS. Additionally, they are involved in activities like pipeline management, pod checking, and error logging, which could suggest areas for further improvements.

I have more than three years of experience working with Amazon EKS.

I would rate the stability of Amazon EKS ten out of ten, indicating it is highly stable.

I would rate the scalability of Amazon EKS an eight out of ten, suggesting it has high scalability.

I do not have experience contacting Amazon's technical support.

I was not involved in the setup of Amazon EKS.

I would recommend Amazon EKS to other people for various reasons. That said, I also rate this solution seven to eight out of ten overall.

Amazon EKS can be used to implement and create clusters. It is also used to deploy and secure the already configured applications. EKS is a cloud-based container management service that integrates with Kubernetes to deploy applications. It automatically manages and scales clusters of infrastructure resources on AWS with Kubernetes.

EKS eliminates the need to install, operate, or maintain a Kubernetes control plane on AWS. Amazon handles everything. We just need to know how we can make it more secure, and we can use it to deploy your applications. It scales automatically, making it one of the best services.

Assigning roles and responsibilities to interact with a created cluster as a user over a command prompt is cumbersome on AWS. Initially, we create a user to interact with a cluster. Since everyone can't use the cluster, we need to assign some permissions to that specific user. It is very cumbersome to assign permissions to users to interact with a cluster. We always get errors, and it takes many days to resolve that permission issue before the user can start interacting with the cluster.

I have been using Amazon EKS for eight years.

Amazon EKS is a stable solution.

Amazon EKS is a scalable solution.

The solution’s technical support is good.

The solution’s initial setup is easy, but assigning permissions to users is difficult.

Amazon EKS is not a cheap solution.

Google Cloud Platform has a service similar to EKS called GKE. It's very easy to implement permissions in GKE as compared to EKS.

Overall, I rate Amazon EKS a seven out of ten.

I use Amazon EKS for telco event monitoring.

My company found Amazon EKS beneficial in terms of the scalability and stability of event monitoring.

What I found most valuable in Amazon EKS is its maturity as a cloud computing technology.

An area for improvement in Amazon EKS is the user experience. The platform could be more user-friendly. Only an expert can manage and use it.

I've been using Amazon EKS for four years.

The stability of Amazon EKS is a ten for me.

Scalability-wise, Amazon EKS is a ten. My team didn't have any problems scaling it.

I had some issues with Amazon EKS. The technical support team found the problems difficult to solve at the time, so support-wise, it's a nine out of ten. Support is not perfect.

Positive

I didn't do the initial setup for Amazon EKS, so I have no idea how easy or difficult it is.

I saw ROI from Amazon EKS.

Amazon EKS has fair pricing. It's better in terms of pricing than other platforms.

I advise anyone planning to use Amazon EKS to do the training because it's initially tough to use the platform.

I rate Amazon EKS as nine out of ten.

Our client in the healthcare industry has multiple clinics and patients who use the solution to interact with their portal and insert patient details. Patient information is managed via databases created in the solution. 

We are still exploring how the solution benefits us because we are enhancing many things on the application side including bug fixes or other items at the code level. 

On the cluster side, we are exploring options to enhance application performance. We are not sure if the solution has created a drastic change, but before we were able to perform and now we are performing well. 

The solution's Autoscaler option allows for an increase in worker notes whenever particular thresholds are exceeded. In our client's case, this is beneficial because the application sits idle the whole night and peaks in the morning hours of 9-10 am as everyone starts interacting with it and processing their workload. 

The solution is quite intelligent and is enhanced every day. They recently introduced a carpenter service that provides added advantages and are working on auto-scaling enhancements which have already allowed us to scale up our Kubernetes Clusters. 

The solution should include a popup for clusters so that all relevant information is visible at the bottom of a page. 

When clusters exist or are running, there isn't much detail on the first phase so navigating and clicking on different options is required to search for relevant information. 

I have been using the solution for three years. 

I really like the stability of the solution. 

We are using the solution to its full capacity to manage various environments and clusters that segregate our client's workload.

The solution is scalable and includes the ability to instruct a cluster to automatically upscale or downscale depending on thresholds written in the code. 

Support is quite good. I haven't used technical support for this solution but have raised tickets for other Amazon products such as IAM or S3 and received help with documentation and tutorials. 

I started my journey as a DevOps engineer with this solution per our client's requirement. 

I was not involved in the initial setup because all customers already had the solution in place before I started interacting with them. I know that setup requires streamlining but is quite easy and just takes time. 

I use some pipelines to deploy workloads such as Terraform or Argo CD where I build artifacts or codes that interact with the solution. Whenever a merge occurs, the pipelines get triggered and automatically deploy in the development environment. If test pieces pass, then they move to the next phase and are deployed on the production level. 

A team of five would be a good fit for a mid-level customer because they can simultaneously work on writing home scripts for the EKS Cluster, building the whole network, and reviewing existing queries. A larger company might require more developers. 

The solution is quite costly and developers will start exploring other solutions or moving their workloads to other clouds if costs aren't reduced.

Our client pays the licensing fees so I don't have specifics about its cost, but I hear that the solution is expensive so I am rating it a five out of ten. 

We are analyzing the solution's behavior but might switch to ECS which provides dedicated resources to an application and runs on its own. 

If you are interested in implementing the solution, first refer to the documentation or existing use cases. 

For example, a streaming company similar to Netflix can adopt and modify a use case related to the Amazon portal. There are resources that help with deciding to implement the solution. 

I rate the solution a nine 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.

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.