What advice do you have for others considering Amazon EKS?

Amazon EKS requires maintenance on my end to continue functioning; we have to do upgradation from time to time since every Kubernetes version is only valid for one year. On a scale from one to ten, I rate Amazon EKS a seven out of ten.

Amazon EKS is easy to use, and you don't experience the problems that you encounter with some solutions like EC2 containers or S3 buckets. The support for AWS tools integration with Amazon EKS has influenced our management process significantly. The cloud affects everything, with probably 80% of our stuff in the cloud, mainly in AWS, though we have some in Google Cloud and Azure. In my role, I don't set anything up; I set up test disaster scenarios and have teams practice against those scenarios. We have encountered challenges during that migration process, and we utilize our AWS dedicated person whenever something arises that we can't handle or don't understand, so we can seek their help. Amazon EKS helps us manage complex workflows effectively. On a scale of 1-10, I rate Amazon EKS a 10.

Regarding self-healing nodes in Amazon EKS, I have not worked on that self-healing feature.For automated patching in Amazon EKS, I have not used that feature. Regarding disadvantages of Amazon EKS compared to competitors in the market, I think every cloud provider has the same Kubernetes engine and worker nodes. However, I believe AWS provides a more user-friendly environment, which is why many of our customers are trying to deploy their infrastructure or applications on AWS. I do not think there is any specific reason not to prefer Amazon EKS. I have not integrated IAM tools with Amazon EKS yet, but my other teams have. I think they used Okta, but I'm not certain about it. I have some demos from a long time ago, but I think Okta is for SSO. On a scale of one to ten, I rate Amazon EKS a nine out of ten.

Our organization maintains a strong team. For major projects, we first work on the architecture perspective. With well-designed architecture, 90% of potential problems are prevented. Being a managed service, we focus on security and managing node services, along with the application perspective. We are not concerned about the Amazon EKS cluster setup as it is a managed service. We only need to add nodes and utilize the features Amazon EKS contains. This reduces our effort and is very helpful for our organization. The reviewer rated Amazon EKS 10 out of 10.

I would recommend Amazon EKS to other people because it is useful, and I believe they will benefit from using it. Based on my extensive experience with the product in my recent project, I rate Amazon EKS 9 out of 10.

I have not utilized Amazon EKS's integration with IAM. I do not really integrate Amazon EKS with other AWS services; our current application would work with any Kubernetes platform, whether it is Amazon EKS, Google Cloud, or any other self-hosted Kubernetes cluster, most likely with some minor tweaks. We do not use any specific Amazon EKS APIs or functionality, so I do not have anything to share about integration capabilities. My personal rating for Amazon EKS is six out of ten, as it really depends on personal preference.

I am using RDS, EC2, S3, Route 53, and a load balancer alongside Amazon EKS. The overall rating I would give Amazon EKS is 8 out of 10.

Amazon EKS's support for AWS tools integration has positively influenced our application development and management process. In 2023, when Johnson & Johnson segregated to form Kenvue, our team was responsible for building the entire DevOps infrastructure. For any startup implementing Amazon EKS cluster for infrastructure or DevOps needs, the solution is excellent. It minimizes configuration time and offers a user-friendly experience that allows even less technically skilled individuals to complete basic cluster setup tasks. Our entire Jenkins pipeline is fully onboarded on Amazon EKS cluster, which we use as a fully managed cluster for our CI/CD workflow. End users, unaware of the backend operations, benefit from Amazon EKS's management of scalability and auto-scaling capabilities. I would rate Amazon EKS 8 out of 10. While it excels in usability, scalability, and high availability, there is room for improvement. The addition of ready-made templates, similar to EC2's default security group feature, would enhance the user experience for newcomers. Integration templates for new users would be a valuable addition to the service.

Within the last 12 months, I have only been working with Amazon EKS. Currently, I have not been working with anything else other than Amazon EKS. For the automated patching feature of Amazon EKS, we currently use EKS baked AMIs, which are straightforward to integrate with the Amazon EKS cluster. If we want to add additional packages or anything by boot time, it is very simple to do so while working with Amazon EKS. We can utilize a user data script to perform any patches, software upgrades, or installations, all accomplished at the instance creation time using EC2 node templates. On a scale of 1-10, I rate Amazon EKS an 8.

On a scale of 1-10, I rate Amazon EKS a 9.

I am not aware of the automated patching feature in Amazon EKS. I work with Amazon EKS and am still currently working with it. We use Kubecost for managing Amazon EKS, which is an external tool we use to find all the healthy status, memory utilization, cost, and all for our EKS cluster. My advice for organizations considering Amazon EKS for their environment is to proceed with it, especially if they are trying for a microservice architecture. It's already very good, with no flaws. Just one thing is to have a look at the cost of the instances they are trying to provision. I rate Amazon EKS 10 out of 10.

We will apply it because it's easy to get out. We can easily integrate it in your application. It also has the most documentation out there. I would advise it.Currently, we are just following the best practices with Amazon EKS. We follow the usual best practices or workflow with Amazon EKS and load balancing. In comparison, the latency is a bit high with Amazon EKS. When we were researching about a year ago, Google offers almost forty milliseconds delay to Mongolia, as Amazon EKS in Hong Kong offers sixty milliseconds delay. That was the only downside from not choosing Google over Amazon EKS. Other than that, Amazon EKS has a lot of services. On a scale of 1-10, I rate Amazon EKS a nine out of ten.

Based on my experience with Amazon EKS support, I would rate it a nine out of ten overall.

The current stuff I am working with has been Kubernetes and building out operational software using Kubernetes. I was actually reviewing Nutanix as an option for some of the stuff I was building out. Mainly on-prem, we are doing production work with a number of customers. We support them, we run an operational arm as well. I have been involved in platforming on Kubernetes, but we happily support any variant. We are cloud agnostic. So these distributions, we would use Amazon EKS or AKS, but not for long. The driver in Rancher, as long as I do not have anything extremely different or complex, works completely the same whether I am driving the application onto Amazon EKS or onto a local on-prem. We have not been using the automated patching. If we were in anger, we do not run the stuff long enough in Amazon EKS at the moment. Really, it is just up in demo and then torn down again. A lot of the stuff is being driven from other automation anyway, more infrastructure as code stuff. So that actually just gets driven completely in there. I think that Amazon, every other provider, is adapting to the changes in the market now because the major cloud benefits are now fully saturated. Nobody else is going in for those benefits. They are starting to hit the reality of regulated technologies that are high value cannot be under a single provider. So a single cloud provider is not sufficient to support critical industry anymore. You have to have either multiple cloud or hybrid just to meet regulation in the future. So that constrains some of the flexibility. But the clouds are all working towards more on-prem extension, that sort of thing to make it more feasible. I would rate Amazon EKS a six out of ten. I have a particular penchant for not actually overscoring anymore because of the way that people use this stuff. In other words, I consider adequate doing what it says they claim it to do. So that is a five or a six as they did what they said they would do. There is nothing wrong with that. It is what we agreed. I paid for it, they delivered it. I am satisfied.

The integration of Amazon EKS with IAM is easy; if you have the right policy in place, you can create a role from the policy and then apply it to the application that you are using. It provides a way to use IAM to provision the software and infrastructure portions, as well as integrating application users into AWS IAM, making it very easy to implement if you know how to do it. The influence of EKS's integration with other AWS tools on application development and management processes is significant; EKS itself is just the infrastructure. Application development requires the right tools with Amazon EKS, as it only provides a place to deploy things, and not the entire development cycle or management of workstations and servers. You must use something on top of Amazon EKS to fulfill the development cycle or CI/CD pipeline. Once the CI/CD pipeline is developed with Amazon EKS as the deployment platform, it becomes easy for developers to develop and test applications in the cluster. I am not exactly sure about the pricing of Amazon EKS, but I think it is priced at the instance level, meaning EKS itself is not that high in price. However, whatever instances are used for Amazon EKS will determine the actual costs, particularly the traffic coming into the cluster. Currently, I am not working with any software other than Amazon EKS, but we have plans to utilize some other applications, not just Amazon EKS, involving other services of AWS. On a scale of one to ten, I rate Amazon EKS an eight.

Regarding the automated patching feature for Kubernetes clusters in Amazon EKS, I don't know any patching feature. On a scale from one to ten, I rate Amazon EKS an eight.

It is a very well-known product, and there are many clients in the market who are using Amazon EKS, so it is the best service offered from AWS. I rate it a nine out of ten. At the moment, whatever is required in Amazon EKS is already there.

The integrations with IAM and Elastic Load Balancing are fundamental aspects. EC2 is the most important integration, and IAM is very strong in Amazon EKS, stronger than in other clouds. However, I need to compare it regularly as this landscape changes daily. The ELB and all the load balancing capabilities are quite strong in Amazon architecture and Amazon EKS architecture as well, so it integrates efficiently. I miss the flexibility to use other options, but I understand why they integrated it so tightly into their platform. This isn't only an Amazon issue; it also occurs on GCP and other platforms, including Azure. Overall rating: 9 out of 10.

I have moved to pre-sales activity now. I am selling Kubernetes Engine from Amazon. I can rate Amazon EKS as nine because I just need to see some improvement. I want to be a reference for Amazon. The overall rating for Amazon EKS is 9 out of 10.

We are using a cloud deployment model. On a scale of one to ten, I rate Amazon EKS an eight.

I suggest understanding the entire form before understanding Kubernetes. I would rate Amazon EKS as a seven out of ten because Kubernetes across all CSPs is complicated. I do not think it is an easy technology to give it anything more than a seven.

Overall, I rate Amazon EKS as a nine out of ten. It's a very stable and reliable product.

Overall, Amazon EKS is a great technology, but the knowledge required to use it is scarce. It is a skill in itself, and developers must undertake multiple roles, which can be difficult. I rate Amazon EKS a seven because it is not easy for developers to configure without a solid base of knowledge.

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.

If you have the money, I would recommend the EKS product to other users who are looking into implementing it. It's a good tool. It really takes some of the management burden off your back. Overall, I would rate it an eight out of ten.

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.

Some of the Kubernetes clusters were on Amazon, GCP, and Azure. I used most of them on-premises. I installed the Kubernetes cluster in my own environment. Overall, I rate the solution ten out of ten.

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.

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.

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.

Overall, I rate Amazon EKS a seven out of ten.

I would recommend the solution. Overall, I rate it a nine out of ten.

I rate Amazon EKS a nine out of ten.

I rate the overall product a seven out of ten.

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.

Review the organization's strategy with your strategy, whether it is oriented to the portability of your applications. Overall, I would rate Amazon EKS a nine out of ten.

I would recommend Amazon EKS to other users. Overall, I rate Amazon EKS an eight out of ten.

I rate Amazon EKS nine out of 10.

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.

I rate the solution as an eight. I advise others to use EKS ETL instead of AWS command prompt while deploying it.

I would rate the tool a ten out of ten. The product is very easy to use since it is based on Kubernetes. It is a great tool for complex environments with multiple applications.

In the internal cluster, we have four hundred people working with Amazon EKS. We have a lot of customers running billions of transactions. Overall, I rate Amazon EKS a nine out of ten.

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.

I would rate this solution as eight out of ten. I highly recommend Amazon EKS.

I rate the solution a nine out of ten and recommend it to others.

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.

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.

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.

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.

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.

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.

I have found OpenShift to be a better tool and I would recommend it. I rate Amazon EKS an eight out of ten.

I recommend this solution to others who use the AWS cloud. I rate Amazon EKS a ten out of ten.

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.