Amazon EKS Reviews

We use Amazon EKS to manage containerization within our microservices environment.

The product's most valuable features are scalability, observability, and performance.

They could add logging features. At present, we use external tools to increase and decrease the number of instances.

We have been using Amazon EKS for three years.

It is a stable service. We never encountered system downtime.

In organizational environments, especially when utilizing the console, EKS is the primary choice. Out of ten clients, approximately eight opt for EKS due to its scalability and robust features.

We contacted AWS support for EKS when we encountered difficulties connecting to private subnets. The support team guided us through the necessary steps to address these issues.

Scalability and security considerations drove the decision to migrate to EKS from another product.

The initial setup was straightforward, especially when Terraform was utilized to generate the setup. We must make minor adjustments, such as changing the name and configuring VPN settings. Overall, it's a relatively easy task for me.

The platform is worth the investment.

The product pricing depends on the specific requirements. For instance, clients between $3000-$4000 per month might find the pricing reasonable, with clusters priced around $70 to $80 plus additional costs. However, the actual pricing can vary based on the number of services utilized.

With numerous tools and plugins available for EKS like Graphite and Prometheus, users can effectively manage logs and monitor performance.

For beginners, it's essential to grasp the fundamentals of Docker and containerization and understand how containers operate. Once these basics are clear, the next step is to familiarize oneself with Kubernetes and container orchestration concepts.

I rate it a nine out of ten.

We use this solution for containerization and push containers into the EKS or CI/CD pipeline in the DevOps pipeline. It's very easy and well-managed for autoscale as we can manage our node groups. In addition, we can tailor autoscaling to our needs.

Amazon EKS with AWS is very good because we can connect our AWS Kubernetes Services with our CI/CD pipelines. We can integrate our EKS with our CloudWatch and Grafana, and other monitoring services are also available. We can also monitor as per our requirements.

The best solution is in AWS, in Elastic Kubernetes Services. We have general control if we want to give access to any user. Also, whenever we push a container or image, we can create any ingress and then connect to our cluster by the Load Balancer directly.

It is very easy, and we can deliver access to customers or users. Also, we can autoscale for any deployment or compute service. In addition, the control panel is completely managed by AWS, and we only have to think about a data plan and what type of deployments, services, and DaemonSets we need.

The main area of improvement is that a cluster is required on-premises, which takes a lot of time. For example, we must drain the total nodes during an upgrade from version 1.21 to version 1.22 with on-premises. After draining the total nodes, our container will shut down, and it will be recreated after upgrading. But with the AWS Kubernetes Services, the upgrade from version 1.21 to 1.22 is completed with one click. It's straightforward for the users.

In any secure services, nodes are working on the EC2 services. Whatever the EC2 services, the specified AMI is available. This AMI is an auto-security package that is automatically upgraded per the company's need. It is also secure.

We have used this solution for one year and use versions 1.15 to 1.22. It is deployed in the public cloud only, in AWS. We were initially working on an on-premises basis of Kubernetes and started working in Elastic Kubernetes in AWS. It is a managed service, and its control panel is managed in AWS. We have to work for our data plan only.

We have about 20 users pushing their container to Elastic Kubernetes Cluster. Most companies want source codes like Python, Node.js, and Java and push them to the Elastic Container Services. It makes it easy for the CI/CD pipeline to build and push images to Elastic Kubernetes Services. We recently started the containerization in Elastic Kubernetes Services.

Regarding technical support, we have the job, role, and responsibilities within our company.

If there is an issue, we must determine whether the solution is working correctly or not. We check if our node group has more or less workload than we need and if the autoscale is defined correctly. We can degrade these instances per our requirement if the node group is less. We added Grafana and Prometheus to monitor the total CPU, memory, and nodes. We can monitor requests, CPU utilization, and whether our node is behaving correctly or if we need any more memory. We also look for any issues with the HTTP request or time out.

The calculation of the pricing is dependent upon instance type. So when we make a cluster without defining any instance type, it will default enter a large instance type. So as per our requirement, we can create our node group and define our instance types per our workload.

I rate this solution a nine out of ten. Amazon EKS is the best service because it has proper security packages and manages AMI. Also, I'm working on GCP and have seen GKE services. With Amazon EKS AWS, we can do a lot of integration with our Kubernetes Cluster.

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

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.

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.