Try our new research platform with insights from 80,000+ expert users
Phat Chau - PeerSpot reviewer
Solution architect at EASY CREDIT Vietnam
Real User
Top 5
Stable product with valuable monitoring features
Pros and Cons
  • "It has valuable monitoring and insights features."
  • "The product’s pricing needs improvement."

What is our primary use case?

We use Amazon EKS as an APM tool for the environment while migrating the monolithic architecture to microservices architecture. It helps us to test product functionality in a particular environment.

What is most valuable?

We don’t have to manage a bunch of infrastructure. Additionally, enabling auto-scaling for both outgoing and node work helps us optimize the cost. It has valuable monitoring and insights features as well.

What needs improvement?

The product’s pricing needs improvement.

For how long have I used the solution?

We have been using Amazon EKS for more than three years.

Buyer's Guide
Amazon EKS
December 2024
Learn what your peers think about Amazon EKS. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.

What do I think about the stability of the solution?

It is a stable product.

What do I think about the scalability of the solution?

We have 200 Amazon EKS users in our organization. It is a scalable product.

How was the initial setup?

The initial setup process takes a few minutes to complete. It requires a team of seven executives to work on the deployment.

What was our ROI?

The product generates a return on investment with the help of OpEx and CaPEx licensing models.

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

Amazon EKS is expensive.

What other advice do I have?

I rate Amazon EKS a nine out of ten.

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.
PeerSpot user
reviewer2139186 - PeerSpot reviewer
Senior Industry Principal at a tech services company with 10,001+ employees
Real User
Top 10
Good auto scaling and service discovery abilities
Pros and Cons
  • "The most valuable features of Amazon EKS are its auto scaling ability and the ability for service discovery."
  • "Amazon EKS's vulnerability management of data could be improved."

What is our primary use case?

We have a service hosting platform, and we use Amazon EKS for hosting web services.

What is most valuable?

The most valuable features of Amazon EKS are its auto scaling ability and the ability for service discovery.

What needs improvement?

Amazon EKS's vulnerability management of data could be improved. Also, concerning vulnerability and version upgrades, many more things could be pulled into the control plane rather than keeping it in the data plane and having the users figure out how to upgrade their portions.

For how long have I used the solution?

I have been using Amazon EKS for five years.

What do I think about the stability of the solution?

Amazon EKS has good stability.

What do I think about the scalability of the solution?

Amazon EKS's scalability is very low. Quite a few people are using the solution in our organization.

How are customer service and support?

We had no issues contacting Amazon EKS's technical support and usually got the necessary support. However, as with any Kubernetes installation, only the control plane is covered by Amazon, not the data plane. So if there are issues on the data plane side, Amazon cannot be of much help.

How was the initial setup?

Amazon EKS’s initial setup was moderately easy. Amazon EKS's deployment was fast. We took the help of an automated deployment system, and the deployment was done in a couple of minutes.

What was our ROI?

We have seen a return on investment with Amazon EKS.

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

Amazon EKS’s pricing is ok compared to its competitors.

What other advice do I have?

Amazon EKS is a good platform to use, but scale up before you start deploying in industrial quantities.

Overall, I rate Amazon EKS an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Amazon EKS
December 2024
Learn what your peers think about Amazon EKS. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
MinhTran2 - PeerSpot reviewer
Technical Architect at Kyanon Digital
Real User
Top 5Leaderboard
Auto-scales efficiently and is good for mapping user content
Pros and Cons
  • "I like its auto-scale feature very much."
  • "The overall stability of the product should be improved to prevent any loss of data."

What is our primary use case?

I only use it to define multi-tenants and define infrastructure.

How has it helped my organization?

Our company has around ten people using Amazon EKS off-site and on-site.

What is most valuable?

I like its auto-scale feature very much. Moreover, it is easy to determine my course of action with many features available on EKS. However, I do have some concerns with Microsoft Edge. Overall, I find EKS to be a valuable solution.

What needs improvement?

The managed services of Amazon EKS could be improved. The system should have a closed-loop feedback mechanism to address any issues that users may face.

Moreover, the overall stability of the product should be improved to prevent any loss of data.

For how long have I used the solution?

I have been working with Amazon EKS for two years now, and mainly use the Command Line Interface (CLI) version.

What do I think about the stability of the solution?

It is a stable solution.

What do I think about the scalability of the solution?

It is a scalable solution for our services.

How are customer service and support?

The response time of customer service and support is quick.

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup is easy. I had some errors initially, but they were easy to terminate.

What about the implementation team?

Our in-house team deployed it. It only took three days to set up and run a big infrastructure.

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

I would like a cheaper version of it.

What other advice do I have?

Amazon EKS is good for managing and providing various services, and for using and mapping user content.

I would rate it a nine on a scale of one to ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Shriniwas-Gadage - PeerSpot reviewer
VP at a tech vendor with 11-50 employees
Real User
Provides autoscaling functionality for container deployment
Pros and Cons
  • "EKS provides autoscaling functionality."
  • "Setup depends on what kind of architecture you have"

What is our primary use case?

We mainly use EKS for containers. We use Kubernetes for scalable deployments.

We're using EKS because our customers requested it. They wanted autoscaling functionality. We have our own product, and we deploy it for our customers in Amazon cloud.

The containers are built, registered, and then kept in a repository at the docker site. Our IT department has an account there. From there, it's exposed and we use the Amazon template surveys and cloud formation template. Then, our IT team creates CFTs. The scripts are run, and the containers are deployed from there.

It's a hybrid solution.

What is most valuable?

EKS provides autoscaling functionality.

For how long have I used the solution?

I started using EKS about eight months ago.

What do I think about the stability of the solution?

It's reasonably stable. EKS is used with Fargate.

What do I think about the scalability of the solution?

From what I understand, it's scalable. I haven't heard of any issues.

How was the initial setup?

Setup depends on what kind of architecture you have.

It depends on the script that's prepared. Once the script is done, just one person is needed for deployment.

What about the implementation team?

We have an internal team that takes care of deployment. They're a specialized team.

What other advice do I have?

I would rate this solution as eight out of ten.

My advice is that not every architecture can fit into EKS. You have to really evaluate whether EKS is suitable for the kind of design and architecture you have. Evaluate it first and then attempt it.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Practice Director, Global Infrastructure Services at a computer software company with 10,001+ employees
Real User
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
PeerSpot user
Patryk Golabek - PeerSpot reviewer
CTO at Translucent Computing Inc
Real User
Top 10
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.
PeerSpot user
reviewer1805982 - PeerSpot reviewer
Solution architect at a tech services company with 51-200 employees
Real User
Top 5Leaderboard
Offers horizontal and vertical scaling and useful for cloud-native applications
Pros and Cons
  • "Amazon EKS is a useful solution for modern, cloud-native applications. It offers both horizontal and vertical scaling, which is a big advantage. The tool can also help manage costs while maintaining high availability."
  • "The main thing to improve with Amazon EKS is the price. However, these services can be very expensive. For example, in countries like Turkey, the cost is too high. That's why we offer our cloud solutions locally. We developed hybrid solutions, but their prices are still very high."

What is our primary use case?

The use case for Amazon EKS is for a payment gateway corporation whose applications run on microservices. Their software team develops cloud-native applications. They use Amazon's public cloud for these applications but find it expensive. They want a less expensive solution for their customers.

We suggest using Amazon EKS open-source solutions. By using these solutions on-premises, they don't have to pay Amazon. 

What is most valuable?

Amazon EKS is a useful solution for modern, cloud-native applications. It offers both horizontal and vertical scaling, which is a big advantage. The tool can also help manage costs while maintaining high availability.

Integrating Amazon EKS with other AWS services is easy if you know how to connect your applications and understand programming. It depends on how your application uses modern programming languages.

What needs improvement?

The main thing to improve with Amazon EKS is the price. However, these services can be very expensive. For example, in countries like Turkey, the cost is too high. That's why we offer our cloud solutions locally. We developed hybrid solutions, but their prices are still very high.

What do I think about the stability of the solution?

I rate the tool's stability a nine out of ten. 

What do I think about the scalability of the solution?

The solution is very scalable. We have two customers for Amazon EKS. 

How are customer service and support?

We don't use support. Our customers use it. 

How was the initial setup?

The tool's deployment is easy. The deployment process is very simple. First, create an account. It's very organic. After that, choose the service that will be used for the project and create new services. Provide your credentials to connect to the environment. If you want to use a private link, you'll need to use a private connection.

What other advice do I have?

I rate the overall product a nine out of ten. If you want to start quickly and have time constraints, you can use Amazon solutions because no time or effort is needed to prepare your environment for the market, and no hardware or infrastructure requirements are required. 

It can affect team productivity with a few customers. Productivity depends on the customers' knowledge. If their developers or software team are familiar with using hyperscale issues, it is very productive to use it.

If you need off-site backup solutions, object storage, or to check your data's secondary version for disaster recovery, you can use AWS Backup or Amazon EKS service, like S3 buckets. It's very useful.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
Head of .NET Department at Evozon
MSP
Top 5Leaderboard
The services are flexible, and they have data centers worldwide
Pros and Cons
  • "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"

What is our primary use case?

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. 

What is most valuable?

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

What needs improvement?

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

For how long have I used the solution?

I've been using Amazon EKS for five years.

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

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.

How was the initial setup?

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.

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

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

What other advice do I have?

I rate Amazon EKS eight out of 10. 

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.
PeerSpot user
Buyer's Guide
Download our free Amazon EKS Report and get advice and tips from experienced pros sharing their opinions.
Updated: December 2024
Buyer's Guide
Download our free Amazon EKS Report and get advice and tips from experienced pros sharing their opinions.