We changed our name from IT Central Station: Here's why

Amazon EKS OverviewUNIXBusinessApplication

Amazon EKS is #6 ranked solution in Container Management software. PeerSpot users give Amazon EKS an average rating of 8 out of 10. Amazon EKS is most commonly compared to OpenShift Container Platform: Amazon EKS vs OpenShift Container Platform. The top industry researching this solution are professionals from a computer software company, accounting for 22% of all views.
What is Amazon EKS?

Amazon Elastic Kubernetes Service (Amazon EKS) is a fully managed Kubernetes service. Customers such as Intel, Snap, Intuit, GoDaddy, and Autodesk trust EKS to run their most sensitive and mission critical applications because of its security, reliability, and scalability.

EKS is the best place to run Kubernetes for several reasons. First, you can choose to run your EKS clusters using AWS Fargate, which is serverless compute for containers. Fargate removes the need to provision and manage servers, lets you specify and pay for resources per application, and improves security through application isolation by design. Second, EKS is deeply integrated with services such as Amazon CloudWatch, Auto Scaling Groups, AWS Identity and Access Management (IAM), and Amazon Virtual Private Cloud (VPC), providing you a seamless experience to monitor, scale, and load-balance your applications. Third, EKS integrates with AWS App Mesh and provides a Kubernetes native experience to consume service mesh features and bring rich observability, traffic controls and security features to applications. Additionally, EKS provides a scalable and highly-available control plane that runs across multiple availability zones to eliminate a single point of failure.
EKS runs upstream Kubernetes and is certified Kubernetes conformant so you can leverage all benefits of open source tooling from the community. You can also easily migrate any standard Kubernetes application to EKS without needing to refactor your code.

Amazon EKS was previously known as Amazon Elastic Kubernetes Service.

Buyer's Guide

Download the Container Management Buyer's Guide including reviews and more. Updated: January 2022

Amazon EKS Customers
GoDaddy, Pearson, FICO, Intuit, Verizon, Honeywell, Logicworks, RetailMeNot, LogMeIn, Conde Nast, mercari, Trainline, Axway
Amazon EKS Video

Amazon EKS Pricing Advice

What users are saying about Amazon EKS pricing:
"The solution is more expensive than other competitors and does not require a license."

Amazon EKS Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
ITCS user
CTO at Translucent Computing Inc
Real User
Top 5Leaderboard
Easy to use, with reasonable pricing and good stability in the latest versions
Pros and Cons
  • "The solution is easy to use."
  • "They need to work on the Amazon plugins on the Kubernetes cluster."

What is most valuable?

The value is for me that it's a community product. We don't have to rely on the ECS services. 

What is new right now is Fargate. Fargate has the ability to abstract from the clusters. Amazon said that using the cluster is too complicated for people. Therefore, what they do right now is they have a service that sits on top of the cluster that doesn't even know it's a cluster. It abstracts it for you. Fargate is the ability to deploy it into the cluster, which specifies what you want to deploy and it takes care of the cluster provisioning and deployment for you. The tool just abstracts you away from the cluster, so you don't even know that you're using a cluster, which is good for people that don't want to learn the technology, the infrastructure.

The solution is easy to use. You don't have to care about the servers or the cluster. You really just say, I want to deploy this application A. You just find the application, click a button, and Fargate deploys it to a cluster for you.

They really want to get away from the idea that you made your own cluster. They really want to push you a bit higher up the layer, more of an abstraction layer.

Due to Kubernetes, it's easy to move between the clouds, to move those jobs, especially in multi-cloud systems right now. So one of the disadvantages of EKS is because of the technology they use for their machine learning right now and we prefer to have options, like CPU and Google.

What needs improvement?

When we switched to EKS, historically it wasn't good. There were issues with bugs in it. They didn't have managed pools, which means small subsections of the clusters that you divided into pools like a mini-cluster in your cluster. However, now they have managed pools.

For the last several versions, the issue was with their kind of networking plug-in, the security plug-ins, and things like that. That EKS layer on top of the Kubernetes, they add themselves to each cloud, however, only with fewer standards and a little more issues. They need to work on the Amazon plugins on the Kubernetes cluster.

We just updated to a cluster 1.18, but we were on that cluster 1.13 which had many bugs and issues. Moving up to 1.19 in the middle of last year, we had some issues which they had to fix.

One thing that is probably not the greatest in Amazon is the ideology. They really want you to stick to cloud tools. They want you to use the managed version of the databases and our preference is to use the Kubernetes-managed databases. This doesn't fit well with the AWS philosophy, which is then passed on to the AWS engineers and they push that, push ideology on us as well, saying "You know what, we want you to use this database."

We're not dogmatic. If they want us to use a specific database, we use it, as the cluster is very dynamic. We don't need to deploy a database within a cluster, we can use the cloud database. To us, it's just a connection string, so it's not inefficient for us. It's just based on the client. However, you can see there's a little bit of an ideology dogma baked into the AWS philosophy just to keep you in the cloud. 

For how long have I used the solution?

We've used the solution since it began. It's been a while.

What do I think about the stability of the solution?

Older versions haven't been so stable, however, they have been working on improving the latest solutions and it's getting much better.

The Kubernetes cluster is developed outside of the cloud, the core of it. The core of it has gotten much better and all the plugins that Amazon did, also have gotten better as well. One kind-of drives the other. It's a revolving, iterative process. You just have to be proactive and keep on updating your versions and manage your cluster a little bit better every time.

How are customer service and technical support?

We don't have to deal with technical support at all. We haven't used them in the last six or seven years. There's nothing fundamentally wrong that we've found over the years that we have to call support. Almost everything is self-explanatory on the website. There really isn't a need to talk to them directly.

Which solution did I use previously and why did I switch?

I also have some experience with Kubernetes and Google Cloud. Google Cloud has something called Google Cloud Run, which is very similar to Fargate. Both are trying to make your life much simpler so you don't have to look at the bare-bones infrastructure. It's easy.

What's my experience with pricing, setup cost, and licensing?

The solution offers different pricing models. They charge in different ways  - either per CPU hour or usage based on a machine type. When it comes to pricing, Google may be two cents cheaper, whoever, the difference makes it a bit of a wash. It might mean an extra five dollars or 20 dollars a month. The difference isn't enough to be too noticeable. All of the main competitors charge very competitive pricing. 

That said, when it comes to the CPUs, that's a Google proprietary technology. When we do machine learning, we do prefer working in Google Cloud, as we have the option to expand all the way to CPU and AWS doesn't have that option. It's a GPU-only system. Amazon's also pushing you towards their own machine learning tool, SageMaker, which we don't want to use. We want to use our own tool.

What other advice do I have?

We're not on the latest version. We are three or so versions back.

However, we're almost on the latest version, which may be 1.19. The version's no longer an issue. For us, the issue was that Amazon started with the ECS, the Elastic Container Services. Therefore, while we were using Kubernetes and then Google Cloud, for example, for a while and we had developed all the tools when a client came to us and said they wanted to cluster within the Amazon development cluster. That was the ECS. After that, Amazon added the EKS. Our first deployment in Amazon was on our own deployment of the cluster, not on any services. We didn't want to use the ECS, we wanted to use a cluster. We wanted a managed version, so we don't have to manage it ourselves, due to the fact that it's a little bit of a mess if you manage it.

I would advise new users to make sure that your cluster's secure. Make sure you're using a good networking configuration in your EKS. You need to get the NAT and the router going just on the subnet. You might have to pay for that. There are open-source tools to use, however, you can also pay for their monitoring.

When you have a development pipeline, we suggest having multiple clusters, not just one. Then you can really isolate your production cluster and make it really secure and maybe relax a little bit for your DEV and then QA, as you might want to have more things in there. You just need to make sure you remove those tools from your production box.

It's easier to have multiple clusters and really partition the cluster per environment, development, QA, testing environment, integration testing, whatever, and then you have your production environment, which is really kind of locked down so that nobody has access to it except specific people.

In general, I would rate this solution at an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
ITCS user
Practice Director, Global Infrastructure Services at a computer software company with 10,001+ employees
Real User
Top 5Leaderboard
Great provisioning and basic features with good technical support
Pros and Cons
  • "The solution has very good basic features."
  • "I'd like to see the solution add a service catalog."

What is our primary use case?

I have tried to host the enterprise content management application of IBM FileNet on Amazon EKS. That's the main use case. 

What is most valuable?

The solution has very good basic features.

The provisioning is very good we use it for the containerization of COTS applications.

The product is stable. 

If a company needs to scale the solution, it can.

The initial setup is simple. 

We've found the solution's technical support to be helpful and responsive.

What needs improvement?

There isn't something that is unique or outstanding. 

I'd like to see the solution add a service catalog.

For how long have I used the solution?

I've used the solution for quite a number of years. It's been around three so far. 

What do I think about the stability of the solution?

We've found the solution to be stable. Currently, it's used on standard VMs. If we put it on Kubernetes clusters, it is highly reliable as well as easy to monitor, manage, and operate. It's great.

What do I think about the scalability of the solution?

The solution is absolutely scalable. There are many enterprises running their businesses on this.

I'm not deploying anything for customers or a certain number of users. I'm just doing it for my own purposes. I'm learning about it and I'm trying new things. I propose these ideas to customers for various solutions and the implementations are done by another team, the delivery team, later. I can't speak to how many people ultimately end up using it.

How are customer service and support?

Technical support is very good. There is no issue. There's no delayed response for their support. There's no lack of support. They are very helpful and we are quite satisfied. 

How was the initial setup?

The initial setup is not overly complex or difficult. It's very simple, very straightforward. The instruction guides are all available and it's enough to get a user through the setup process. They are quite helpful guides. 

What about the implementation team?

We have a professional services team that does the job day in, day out. That said, I do it for my learning and I practice something on my own too. Therefore, I am also very capable of handling the initial setup myself. 

What's my experience with pricing, setup cost, and licensing?

We already have costs built into the service given by the particular vendor. If it is on-premise, we buy the software, and we pay some support costs and license costs. However, if it is on the cloud, it is a pay-per-use model. 

What other advice do I have?

I'm an integrator of the solution. 

The solution can be deployed both on the cloud and on-premises. 

We are using the latest version of the solution at this time. I can't speak to the exact version number, however.

I would recommend this solution to others. 

I'd rate the product at a nine out of ten. We're pretty happy with its capabilities so far. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
Flag as inappropriate
Find out what your peers are saying about Amazon, Red Hat, VMware and others in Container Management. Updated: January 2022.
564,599 professionals have used our research since 2012.
Solution Architect / Head of DevOps Engineer at a tech services company with 201-500 employees
Real User
Top 5
Reliable, helpful technical support, and beneficial replication and scaling
Pros and Cons
  • "We do not have to do a lot of administration, such as create virtual machines, or worry about our controllers or nodes going down because the solution is fully managed by Amazon."

    What is our primary use case?

    Amazon Elastic Kubernetes Service (EKS) solution integrates AWS cloud with Kubernetes. Kubernetes is an open-source container technology that is popular right now. It has the ability to replicate applications for scaling.

    How has it helped my organization?

    Having this solution on the cloud has allowed us to focus more on our business because we do not have to worry about our own infrastructure.

    What is most valuable?

    We do not have to do a lot of administration, such as create virtual machines, or worry about our controllers or nodes going down because the solution is fully managed by Amazon.

    You are able to have your applications on the cluster which provides the ability to replicate and scale them.

    For how long have I used the solution?

    I have been using the solution for approximately two years.

    What do I think about the stability of the solution?

    The solution is stable.

    What do I think about the scalability of the solution?

    I have found the solution scalable. 

    This solution is used by the three-person DevOps team in my organization.

    How are customer service and technical support?

    The technical support is very good.

    How was the initial setup?

    The creation of the clusters only takes approximately 10 minutes.

    What about the implementation team?

    We did the installation and configuration ourselves.

    What's my experience with pricing, setup cost, and licensing?

    The solution is more expensive than other competitors and does not require a license.

    What other advice do I have?

    I recommend this solution to others who use the AWS cloud.

    I rate Amazon EKS a ten out of ten.

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    Director Of Sales Marketing at a energy/utilities company with 10,001+ employees
    Real User
    Top 5Leaderboard
    Very user friendly and easy to maintain

    What is our primary use case?

    Our main use case is when our client or the customer would like to have their service on AWS. When the client preference is AWS.

    How has it helped my organization?

    Our company prefers Amazon EKS to ECS.

    What is most valuable?

    The feature that I have found most valuable is that it is very user-friendly.

    What needs improvement?

    I would like to see it a little more stable, more operational, and more convenient to develop.

    For how long have I used the solution?

    I have been using Amazon EKS for about two to three years.

    What do I think about the stability of the solution?

    Amazon EKS is very stable.

    What do I think about the scalability of the solution?

    We have about 500 people in our organization using it. Our technical team for the…

    What is our primary use case?

    Our main use case is when our client or the customer would like to have their service on AWS. When the client preference is AWS.

    How has it helped my organization?

    Our company prefers Amazon EKS to ECS.

    What is most valuable?

    The feature that I have found most valuable is that it is very user-friendly.

    What needs improvement?

    I would like to see it a little more stable, more operational, and more convenient to develop.

    For how long have I used the solution?

    I have been using Amazon EKS for about two to three years.

    What do I think about the stability of the solution?

    Amazon EKS is very stable.

    What do I think about the scalability of the solution?

    We have about 500 people in our organization using it.

    Our technical team for the deployment and maintenance is only five people, one manager and four engineers.

    We are definitely going to continue using this solution.

    Which solution did I use previously and why did I switch?

    For container management, I had been using the IBM SP solution, but frankly speaking I don't like the IBM Cloud.

    How was the initial setup?

    The initial installation was straightforward. It took under 30 minutes.

    What other advice do I have?

    I love dealing with EKS. Personally, I like to deal with the Kubernetes solution.

    On a scale of one to the, I would rate EKS a nine.

    I would recommend Amazon EKS to others.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    Materials Program Management Specialist at a manufacturing company with 10,001+ employees
    Real User
    Overall good functionality, scalable, and supports multi tendencies
    Pros and Cons
    • "Overall Amazon EKS is a good solution in the industry. The solution can support multi tendencies, and network isolations are the key factors."
    • "Amazon EKS is predominately public. However, the government has started to have a lot of interest in Kubernetes and is receiving more education on Kubernetes and Amazon EKS. If we can have the security of Amazon EKS align with the security that is set out by the government it would be much better."

    What is our primary use case?

    We use Amazon Elastic Kubernetes Service (EKS) to manage our containers and to run and scale Kubernetes applications in the cloud.

    What is most valuable?

    Overall Amazon EKS is a good solution in the industry. The solution can support multi tendencies, and network isolations are the key factors.

    What needs improvement?

    Amazon EKS is predominately public. However, the government has started to have a lot of interest in Kubernetes and is receiving more education on Kubernetes and Amazon EKS. If we can have the security of Amazon EKS align with the security that is set out by the government it would be much better.

    For how long have I used the solution?

    I have been using Amazon EKS for approximately six months.

    What do I think about the scalability of the solution?

    Amazon EKS is scalable.

    We are in the process of migrating from OpenShift to Amazon EKS which will be a lot of work to migrate over. We have about over 300 developers who are going to use Amazon EKS in the future.

    Which solution did I use previously and why did I switch?

    We have previously used OpenShift.

    What about the implementation team?

    I did the implementation of the solution myself in my organization.

    What other advice do I have?

    I have found OpenShift to be a better tool and I would recommend it.

    I rate Amazon EKS an eight out of ten.

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    Product Categories
    Container Management
    Buyer's Guide
    Download our free Container Management Report and find out what your peers are saying about Amazon, Red Hat, VMware, and more!