Amazon EKS Reviews

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. 

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 basically a model provided by Amazon that allows you to create and deploy multiple microservices and manage containers. Once the Kubernetes is installed, we can directly create the container, set up ports, and set up new services. We currently have Java containers running.

We have more than 500 people using this solution. We are on version 21.

I like the scalability they're currently providing. Integration was very easy. It was a good experience. 

The connectivity could be better.

I have been using Amazon EKS for more than two years.

It's stable enough. We have had network connectivity issues twice. We weren't able to figure out what went wrong there, and it caused a problem initially. When we restarted it, it began working again.

The scalability is good.

We have called technical support a couple of times. We had an issue with integration with Lambda. But we took the help of AWS and it was resolved.

We have also used the IBM private cloud, but it wasn't user friendly.

Setup can take half an hour to an hour.

For deployment, our technical team was made up of 15 people.

My company paid for the license. 

I would rate this solution 8 out of 10.

I would definitely recommend this solution. It's a very good application, and the scalability is very good.

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

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

I have been using Amazon EKS for five years.

Amazon EKS has good stability.

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

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.

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.

We have seen a return on investment with Amazon EKS.

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

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.

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

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

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.

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.

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

It is a stable solution.

It is a scalable solution for our services.

The response time of customer service and support is quick.

Positive

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

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

I would like a cheaper version of it.

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.

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.

EKS provides autoscaling functionality.

I started using EKS about eight months ago.

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

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

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.

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

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.

Our primary case is using Amazon EKS with all of our data in our MapReduce, map clusters, and our data clusters. And from there, we just input the information using Python and do our analysis using that.

We have problems with setting up virtual environments and installing the right packages. I believe the initial setup could be a better experience and faster customer support.

I have been using Amazon EKS for the past one and half years now.

The stability is excellent.

The scalability is not a problem we currently have five to six thousand employees using Amazon EKS.

Technical support or customer support is good but could be faster.

For us in our company, it is a very straightforward process because they had built a layer that is very useful for the users with just a couple of clicks. But normally, if you ask me in person, I think it is a bit cumbersome.

It can be done in-house but they have to read a lot of documentation from the AWS provider in order for it to make sense.

When you compare it to on-premises it is much better because, with on-premise, we have to look into data security and all these items. Amazon EKS eliminates that and becomes a cost-benefit for us.

On a scale of one to ten, I would give it a six. With the correct technical support individual, you can do well with implementation. If you are not sure about the technical support side for implementation I would wait until you are ready.