Amazon EKS Reviews

I use the solution for its microservices. I used the product in some of my personal projects for deploying applications. From an organizational standpoint, the product is useful for its microservices.

When it comes to Amazon EKS, there are IAM permissions and RBAC. When you create an IAM user, you give the privileges on the cluster level, but there won't be anything inside the clusters. In the clusters and their respective files, you will have to map the IAM user created with the help of AWS. The documentation part of the product is an area of concern that needs to be made easier from an improvement perspective.

I have experience with the tool for the past six to eight months. For some of my personal projects, I have been using the product for a year and a half. I am a customer of the product.

Stability-wise, I rate the solution a ten out of ten.

Scalability-wise, I rate the solution a ten out of ten.

The product's initial setup phase is easy since it is only based on a one-line command to help you set up an EKS cluster.

The product is available at such a huge scale in the market since the resources that are offered under the tool are competitively priced and available at a much cheaper rate compared to other solutions.

One of the aspects of Kubecost and Amazon EKS is that you don't have to manage the master node. The scalability and connectivity between API servers and its resources, including its scheduler and controller, are all taken care of by AWS. Not being easily able to log in to your master node makes things secure.

I found the cluster autoscaler of AWS to be very helpful. It is easier for users since the cluster autoscaler takes care of the nodes, making everything easy for me. With the cluster autoscaler, all the resources are presented to me, so I need not consider any integrations from the outside environment. The aforementioned reasons made it easy for me to set up the software and scale down the resources easily.

I recommend the product to those who plan to use it. Kubernetes is a product from Google, which offers good compatibility. Kubernetes and its compatibility with Amazon is decent enough for users, in my opinion.

I rate the overall tool a ten 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. 

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. 

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.

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

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.

Amazon EKS is for storage, services, and infrastructure. We have about 100 to 120 users on Amazon EKS right now. We'll likely expand by 10 or 15 percent in the next year depending on our customer needs. 

AWS cloud services are flexible and have thorough documentation. AWS also has data centers all over the world.

I would like Amazon EKS to be easier to configure on various environments like Windows or Linux installations

I've been using Amazon EKS for five years.

We use AWS in parallel with other cloud service providers from different vendors, like Azure and GCP. We are not the end customer. It's something we use to deliver services to our customers. We work with a wide range of technologies at the company, which employs around 500 plus people. They work with all major technologies currently available.

Installing Amazon EKS is straightforward. It depends on what needs to be done, but it's not something that takes weeks to deploy. You can do it in a few hours or days. I would need to have a specific scenario to be precise because the steps vary in each installation.

I would like Amazon EKS to be cheaper. Otherwise, it's fine.  

I rate Amazon EKS eight out of 10.