Amazon EKS Reviews

Our primary use case is related to our ecommerce solution, which is very high in terms of data in the database and products. It has one hundred thousand first line items. We developed a system connected with AWS services to translate search keywords into different languages and improve search results accuracy on our ecommerce site.

The scalability has really helped us a lot in enhancing the customer experience and ensuring quick results. The ROI is really good, especially when compared with other services on-premises.

Amazon EKS provides good support. The integration and stability are clear and reliable. The scalability is excellent, allowing us to efficiently handle customer experiences and improve operational efficiency.

Sometimes, we face minor connectivity issues. However, it depends on the applications we are using. Improvement might be needed based on different use cases.

We have been using it since 2015.

The stability of Amazon EKS is clear and reliable.

Amazon EKS's scalability is clear and has improved our operational efficiency a lot.

The customer service and support are good, and we have a paid subscription that provides priority support.

Positive

The initial setup was handled by third parties. It involved some complexities, and appropriate inputs were necessary.

We worked with a third-party team for implementation, including many developers.

We did several ROIs, which showed positive results. It's particularly beneficial compared to investing in hardware.

The licensing cost is acceptable.

Before implementing, ensure thorough research and ROI analysis. The implementation should be handled by experienced personnel.

I'd rate the solution eight out of ten.

I am working mostly on AWS infrastructure services, such as EC2, EKS, RDS, CloudFormation, IAM, and CloudWatch. I have around one year of experience with Kubernetes and have been using AWS services continuously for three years. My responsibilities include working on server storage, containerization, monitoring, and access policies.

Simplifies Kubernetes setup and management.AWS handles cluster upgrades, patches, and availability.Seamlessly integrates with AWS services like IAM, CloudWatch, and VPC.Access to advanced networking, security, and monitoring tools.EKS automatically deploys the Kubernetes control plane across multiple AWS Availability Zones for fault tolerance.

I have around one year of experience using Kubernetes with AWS.

In my project, AWS EKS has shown stability without any issues.

EKS offers excellent scalability, especially compared to Docker Swarm. The ability to scale based on requirements by deploying additional containers is a strong point for Kubernetes.

I have not contacted technical support regarding EKS.

Positive

I have explored Google Kubernetes Service in my personal projects but did not work on any other Kubernetes projects before EKS.

The initial setup is relatively straightforward when using the AWS Management Console. Setting up clusters and nodes is simplified through AWS's interface compared to on-premises. It took approximately 15 to 20 minutes to complete the setup.

I do not have specific details on EKS's pricing and licensing compared to other services. However, in general, deploying in the cloud offers lower latency and high availability and reduces manual intervention and responsibility, leading to some operational efficiencies.

I have worked with Google Kubernetes Service in my personal space but have not evaluated others for professional use.

For large-scale enterprise solutions, Kubernetes is recommended due to its scalability. Despite costing considerations, EKS alleviates the burden of procedural complexities, making it suitable for enterprise-level applications.

I'd rate the solution eight out of ten.

For EKS, we deployed a Django application. The application built the whole image and stored it in ECR (Elastic Container Registry). We stored the code repository in GitHub, but the image was in ECR. We also had another repository for the Kubernetes manifest files. So we were deploying it in a different image, and the code was in a different image. We had a whole pipeline for deployment, from CodePipeline to ECR, and then from ECR to Kubernetes.

I work with different AWS solutions, such as Elastic Beanstalk, AWS Lambda, DynamoDB, and VPC. I use services like EC2, S3, and VPC every day, so I'm not including those. I've also used API Gateway, and currently, I also use AWS Bedrock.

The good thing was the integration of services. The only thing we had to think about was how we were pushing the code to GitHub or Bitbucket. After that, everything was taken care of by AWS. 

Everything was connected: the code and the real-time deployment. Testing was done within the same pipeline using CodeBuild. CodeBuild was handling multiple tasks: testing the code, deploying it to ECR, and then running it on AWS Fargate for development or testing. Once it was working fine, we had an approval stage. After approval, we deployed it to EKS using the command line from the same AWS CodeBuild process.

The scalability of EKS is good. We've compared it with multiple platforms, and we've also worked with GCP. There are more good options available in GCP compared to EKS.

But the good thing about EKS is that we can use it for serverless deployments using Fargate. It gives you two options: deploy on EC2 or deploy on Fargate. EC2 runs 24/7 and costs you money, but Fargate only runs when you need it. So EKS was really helpful for saving costs with that serverless capability.

I would like to see a warm-up time for AWS Fargate, similar to what GCP Cloud Run has. This would improve internal security. I would also really love to see lower costs compared to other cloud vendors. AWS can get quite expensive.

I've been working with EKS on and off for the last two years. Some of the projects were my own, and some were development projects.

They have good documentation and lots of blogs on Amazon AWS, so we mostly follow those. We haven't reached out to technical support directly. We had a plan for technical support, but it took them more time to fully help us. 

Sometimes the issue is on our code side and not on AWS's side. Getting the customer service and support involved in our whole process takes a long time. It's better to research for a few hours and fix it yourself rather than waiting for a week or so.

GKE gives you really good monitoring and logging, where you can see every bit of information flowing in your environment. AWS provides the same thing with CloudWatch, but it's much easier in GKE to see what's exactly going on. So monitoring and the transparency of what's happening would be one thing AWS needs to improve.

The pros of EKS are that it makes deployment really easy. You just need to package your image in ECR, and then everything goes very smoothly. You don't have to worry about running or managing Kubernetes. It gives you a managed control plane, and they replicate the control plane over different regions. So there's very little chance that it will go down. Reliability is really high with AWS.

When we started we had an issue with rollbacks. We had problems because we had to specify certain AWS parameters in order to deploy it properly. We consulted the documentation and resolved it that way.

We did some testing, and that took about one month with it. Then we started with a very small infrastructure on EKS, migrating some of our traditional websites to EKS directly. So, the initial setup took about two months. 

But we didn't use it for microservices; we only used it for two services: one was our platform service, and the other was Redis.

In my case, I handled the deployment part. I had a manager, so I just took his approval and gave him the deployment design. He was overseeing everything, but I was doing almost all the AWS work. The developers were really helpful in making the code run correctly with the image versioning.

Users have to maintain things. For example, we faced an issue where we had a lot of requests coming in, and we weren't ready with enough resources at the time. We had to manually increase the Kubernetes nodes. That was an issue with horizontal scaling. It was our mistake because we didn't automate it.

We shifted from EKS to GKE (Google Kubernetes Engine). We are saving around 20% with that change.

I already have recommended it to many people. If you're using AWS for other services, definitely go with EKS because it doesn't make sense to move to another cloud vendor if you're already using everything in AWS. The integration is really good. You get AWS WAF (Web Application Firewall) on top of it, load balancer, GuardDuty, and Inspector. So security-wise, it's really nice to have EKS surrounded by those security tools.

My advice would be to try to go with AWS Fargate initially. Try to understand how ECR (Elastic Container Registry) works because it also costs you money, so make sure your image isn't too big. And if you can, go with AWS CodeCommit, it makes things very fast. And for EKS, they can use Fargate with EKS as a service. So, users don't have to worry about scalability and reliability. It's totally managed from the user's end.

Overall, I would rate it an eight out of ten. 

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.

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.

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.

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