Amazon EKS Reviews

The main use cases for Amazon EKS are that we use it normally in some new projects to optimize our costs. Instead of having many ECS services running, we prefer to set up a Kubernetes cluster and set everything there. For me, it is primarily for optimizing our resources.

What I find valuable about Amazon EKS is that it helps us manage all the Kubernetes. It isn't the workload, it is the main part of the Kubernetes, the head of all the cluster. Automatic updates are available, and we can set everything we created in AWS in Kubernetes, including IAM configuration. We can create policies such as creating a private endpoint for S3. The integration of Kubernetes with the AWS ecosystem is the best feature that Amazon EKS provides.

The IAM integration in Amazon EKS helps enhance the authentication processes because we can do this in a more granular way. Using IAM, you can set exactly what the service needs. If a service or application needs to upload objects or data to S3, connect to RDS, or perform other tasks, using IAM is the easiest way. The benefit is that it works in a granular way and it's easy to set up and validate. When you examine the permissions and rules to ensure everything has the correct permission at the correct moment, using IAM is perfect because you can validate and set up everything effectively.

Amazon EKS's support for different AWS tools integrations has accelerated our application development because we can think about all aspects comprehensively. We can architect using AWS services and objects, and Amazon EKS accepts this seamlessly. We don't need to translate the idea for AWS. We can write this idea using AWS objects and services, and Amazon EKS corresponds to that. It accelerates projects and is easy to manage because we can use Terraform to implement it.

I am using the self-healing nodes in the Amazon EKS solution. We have a client with a production workload running on spot instances. When a spot or node crashes, Amazon EKS starts a new node and moves everything before the node stopped. This self-healing is excellent because we don't experience disruptions. We don't face situations where a node stops and we need five minutes to start a new one. We use it in specific environments and can observe the difference when enabling or disabling Amazon EKS self-healing.

We are utilizing the automated patching in Amazon EKS. The valuable benefits I have experienced using the automated patching feature for the Kubernetes clusters directly increase security. Kubernetes typically releases patches focused on security rather than new features. It's beneficial because we can focus on our work without constantly thinking about new patch releases or upgrade deployments. Amazon EKS handles this automatically for us.

We face some issues with Amazon EKS when using the node group to control which nodes can start. We have a limitation where we need to set just one kind of instance - only large instances, only small instances, or only extra-large instances. This is a problem. It would be beneficial if we could specify that certain containers or services start on small instances rather than large ones.

I am uncertain whether Amazon EKS supports all LTS versions, and I think this would be something beneficial. Additionally, AWS has great AI features, so when we need to make updates to Amazon EKS, it would be helpful if AI could assist with planning, identifying migration requirements, and considering costs.

I have been working with Amazon EKS for about two years in production. Including study time and other experiences, I have been involved with it for approximately four years.

I faced challenges in the initial stages with Amazon EKS. The main challenge is that when we set up the cluster, it appears as a huge infrastructure just for a small application. When you set up Amazon EKS, it is configured at a large scale by default. You can't start small and gradually expand. This makes sense because for smaller applications, ECS works effectively. If you want a more integrated ecosystem, you can use Amazon EKS. The challenge lies in migrating everything, as you can't start using Amazon EKS on a small scale. It typically requires a big cluster with one, two, or three nodes. We also faced challenges with developers needing to adapt their mindset to the new way of doing things.

I have escalated questions to the technical support of Amazon EKS two or three times, and they always provided good solutions. When we don't understand the questions, we schedule a call to demonstrate the issue, and we always receive the correct answer.

I reached out for technical support with Amazon EKS because we faced issues starting a service. The way we declared the services was incorrect, but we weren't aware of this. We called AWS support for assistance. Another issue involved a security problem that we identified and reported to AWS.

I would rate the technical support of Amazon EKS a 10. The documentation is good, and when human interaction is needed, it's readily available.

From my perspective, I don't see any disadvantages of Amazon EKS compared to competitors in the market. Amazon EKS represents the state of the art. While Google has a powerful engine that offers more granular control, the additional configuration can be overwhelming. Amazon EKS balances the power of custom configuration with ease of setup.

I find the pricing of Amazon EKS complicated because I live in Brazil, where we use reals. With the exchange rate and taxes, the price appears six times higher. However, when viewed in dollars, it offers great features at reasonable pricing. Lower prices are always beneficial, and a reduction in hourly cost or promotional discounts would be appreciated, but the current price-to-benefit ratio is worthwhile.

My advice to other organizations considering Amazon EKS for their environment is to plan carefully. I strongly recommend planning and reading the documentation because Amazon EKS is resourceful and typically offers multiple ways to accomplish the same task. Careful planning, reviewing case studies for comparison, and thoughtful migration to Amazon EKS are worthwhile investments. Overall, I rate Amazon EKS a 9 out of 10.

Public Cloud

Amazon Web Services (AWS)

We are migrating our services into container services. We build websites and all of our products' backends are based on Amazon EKS.

The simplicity and management portal make it a neat solution. You don't have to fiddle around with too many open source tools, as it's just a comprehensive solution.

We use the pipeline, which is critical for us to deploy automatically. This eliminates manual intervention, which is really helpful.

We initially had some issues getting the logging out of it, because what they're providing into CloudTrail is what we get. If we wanted to go in-depth, we had to deploy third-party tools. We did try the sidecar way of getting the logs. Ideally, if the platform was able to provide those kinds of valuable logs, that would be beneficial. Adding enhanced logging capabilities would be a nice improvement.

We have been using the solution for three plus years.

Time to value is good with fast deployment and very good documentation that is really helpful.

I don't personally deal with the costing part, but I think it's a fair amount. That's the only reason we're using it continuously, as otherwise we would have moved somewhere else.

The implementation was done in-house.

On a scale of 1-10, I rate this solution a 9.

Public Cloud

Amazon Web Services (AWS)

My main use case for Amazon EKS is to host one of my AI agents which I built recently in my company. I use Amazon EKS to host my AI agent, which is a sprint report agent that fetches the company's data from Jira and prepares a sprint report for the complete team. The agent runs on Amazon EKS for high availability and reliability, hosted on nodes, and it is running on a GPT OS's model in the back end.

I have designed this agent for high availability on Amazon EKS because if I hosted it on any other platform, there would be chances of downtime. I have set it up in such a way that if there is any downtime, a new node is already up and running so that my use case is not affected and the users can use it seamlessly without any issues.

The best features Amazon EKS offers in my experience are its reliability and high availability, and also the support that AWS provides. The reliability and high availability have helped me specifically because there were some configuration issues at my end for the agent, which caused it to go down repeatedly. Due to the high availability features, every time a node downscaled, a new node was automatically scaled up, ensuring that the AI agent was up. I was able to check the logs and correct the issues accurately thanks to that high availability. Also, AWS support is very helpful; whenever I face issues regarding costing or anything else, I just create a ticket and they assist me in resolving the issues.

Amazon EKS has positively impacted my organization by improving the efficiency and working capacity of my team. It improved efficiency and working capacity because, based on how Amazon EKS works, we are more calm regarding functionality. The reliability allows us to focus on many other tasks, as the infrastructure is maintained by Amazon EKS; therefore, we can divert our attention to other tasks and perform well there as well.

Functionality-wise, Amazon EKS is acceptable, but navigation-wise, it could be improved in the AWS console; it could be more interactive and more intuitive for new users. Also, the pricing can be reviewed as it is sometimes a bit pricey, particularly regarding the extended support when new version upgrades occur that we cannot implement directly due to production workloads, as clusters running on extended support cost six times more, which is something that could be reduced.

I believe documentation could be improved on the AWS website so a new user who is starting with Amazon EKS could work much better with it.

I have been working in my current field for three years.

In my experience, Amazon EKS is stable.

The scalability of Amazon EKS is good.

The customer support of Amazon EKS is good. I would rate the customer support on a scale of one to ten as a seven.

Positive

I have seen a return on investment because the reliability has helped me save time; I can rely on Amazon EKS's reliability and then divert my attention to other tasks, so it has definitely saved my time. I estimate that my team and I save roughly one to one and a half hours a day since using Amazon EKS.

Regarding pricing, setup cost, and licensing, the pricing for the cluster part is a bit higher; the setup cost is acceptable, but the licensing part regarding extended support is also a bit pricey, which I think can be handled or reduced.

Amazon EKS is a good product; if you are starting with Kubernetes, it is a good choice, but the pricing is a bit substantial, so you should review that. Also, regarding the support, there are sometimes cases where you need to upgrade your AWS plans for particular support, which can also be a bit pricey. I would rate this product a seven overall.

Private Cloud

Amazon Web Services (AWS)

There are migration projects where we need to migrate some on-premise services to Kubernetes. In that case, we have used Amazon EKS to migrate our workload. There are two production services that we need to deploy on the cloud, so we chose to use Amazon EKS to deploy them on the servers.

There are multiple node clusters that we have within Amazon EKS. We have different node groups that we have used. Some of them are high performance, some have high-speed hard disks, and some have high CPU. There are multiple node groups that we have provisioned and also enable the scaling within the pod level and within the cluster level. There are multiple features that we have used along with node management.

For streamline, we need to apply GitOps within Amazon EKS. Whenever there is a commit in the deployment-related stuff, we need to deploy the new image on the image repository, and from there, we need to update the kubectl YAML files with the new image tag. We can also choose the Helm charts based, and we can also choose Argo CD for the automated deployments.

We have implemented two things with Amazon EKS. First of all, OIDC-based connectivity between the AWS services to the Kubernetes workload. Additionally, we implemented RBAC. We have used RBAC to provision IAM users to have proper security and a constrained environment so that read-only users can only read the things.

We have used Amazon EKS Anywhere for on-premises deployments, and within Amazon EKS, it has an air-gapped environment where we can deploy the things and manage the local type of Kubernetes.

Managing the production workload in Amazon EKS is highly valuable. It has many features, for example, self-healing, automatic deployment, rollouts, and better management. It is an Amazon managed service, so we need to just focus on the cloud itself.

We have installed Prometheus and Grafana within our Amazon EKS, and we have used DataDog operators as well to have proper production workload management and monitoring management system. We can see the logs, alerts, and everything related to it. We have integrated Slack and email addresses through SES. This is how we are monitoring our production workloads and get alerts based on problems within our production.

The main benefits from using Amazon EKS include it being a well-tested product that we can use to deploy our workload. Its management system is very efficient. We can deploy things very easily and resolve our issues efficiently. It has deep AWS integration and a managed control plane. It has built-in IRSA-based security model for IAM roles. We have flexibility and portability. We can use Helm, Argo CD, Flux CD, Istio, and Linkerd. We can use multiple EC2 machines, such as spot instances and Graviton-based instances that are GPU-powered. These features help us use Amazon EKS for our production environments.

I would appreciate seeing integration between the other services in Amazon EKS. For example, there are now more managed Prometheus and managed Grafana services available last year. I would appreciate knowing more about how AI-based services get integrated with Amazon EKS and what kind of AI automation, healing, or troubleshooting services Amazon will introduce in upcoming releases.

I have been working with Amazon EKS for three to four years.

The setup of the Amazon EKS environment is quite fairly simple, and we can easily automate them using Terraform as well.

Once everything is set and done, there is no maintenance required, which is a very good point.

I did not see any crashes, downtime, or performance issues with Amazon EKS.

We have enabled the cluster-level enablement and auto-scaling in Amazon EKS, and that helped us significantly. Whenever we have peak time, it will automatically manage the node for us, and there are more nodes to manage our workload.

For a few of the cluster upgrades that got stuck, we connect with Amazon tech support, as we have business support with Amazon. We connect with them, and we figure out the problem. They help us to troubleshoot the issue, and we run commands related to Cordon or Taint. With this, we complete our upgrades process.

On a scale of one to 10, I would rate the technical support and customer service of AWS as eight to nine. They are very technical, and they can easily fix things within 20 to 30 minutes.

Positive

I worked with on-premise Kubernetes, and I also worked with Azure Kubernetes, AKS.

I have worked extensively with Amazon EKS, and I have automation scripts ready. Whenever a new client comes to me, I request them to see my previous portfolio, and I show them my Amazon EKS work and how quickly I can set up their Amazon EKS and run the CI/CD so that their workload can get migrated to Amazon EKS. It is quite easy for me now to advocate for Amazon EKS.

We have a big business up and running in Amazon, and we have different AWS accounts: dev, test, and prod. Based on that, there is a root account who is paying the prices for us. The workload and the profit that we are getting, we are satisfied with what it is offering.

The pricing of Amazon EKS depends upon the node group that we are choosing and what kind of auto-scaling that we have implemented. It is totally dependent on those things, including what kind of network bandwidth that we are consuming.

I find the pricing of Amazon EKS reasonable. We actually are going to pay a yearly advanced payment, which helps us save on cost.

Amazon EKS has strong integration with its services. In Azure Kubernetes, it does not have strong, deep integration with its services, for example, Active Directory, Azure Registry, Azure Monitor. Both have their managed control plane and node management. Amazon EKS has a different pricing model - it is per cluster control plane level, whereas AKS is not on the control plane fleet's history. Regarding security, Amazon EKS provides IRSA-based, IAM role-based security, whereas AKS provides directory, Azure Active Directory.

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.

Public Cloud

Amazon Web Services (AWS)

We are going to be using Lambda on the AWS Stack. We are migrating all our on-premises applications to AWS.

Eggplant is going to be on the AWS platform soon. We are using Lambda functions and CloudWatch for monitoring. We are also using Elasticsearch and ELK.

After we move all the applications to the cloud, we're going to move them into Amazon EKS as containers for easy management. It would be the same as how we are using EC2 instances, but in this case, we're going to move all applications to run on containers, Amazon EKS containers.

We use it for common file sharing across applications. I'm not really sure about all aspects as I didn't use it much. We just set it up to make sure all applications can read. The main capability is allowing different applications to access the same file or resources at the same time, providing collaboration capabilities.

The whole platform is easy because once you set it up, it's easy to onboard applications. It's easy to troubleshoot, run multiple clustering, log management, and perform troubleshooting. You can also install other applications, third-party applications, integration, and all that.

It helps with having dedicated nodes for certain functions. If you want to segregate the work instead of using all the nodes, you're able to align and assign which node processes specific applications, jobs, pods, or runs certain pods.

It reduces the deployment time, setup time, configuration time, and is cost-effective. It's very highly scalable.

The main challenge is at the beginning when you're still learning how to set up. The initial setup and knowing how to do it the first time can be challenging.

We had some challenges with the network pods. There were several pods that we had to try plugins for network, and the load balancing for the application we were deploying was quite difficult to manage.

The documentation should be easier to understand for beginners. It needs to be straightforward and easily grouped together because information tends to be scattered.

Some features required a lot of command line changes, especially setting up ingress and load balancers. If there could be a way to do that on a GUI, that would be easier. Having more configuration options on the UI, especially for setting up load balancers and ingress controllers, would be beneficial.

We have been using the solution for three months.

Currently, we haven't really automated the deployment. We are using Jenkins for our work.

Microsoft tools are being used in the bank.

We haven't experienced any scalability issues.

The support is quite friendly and very helpful. The Amazon support is very helpful and very responsive.

Positive

The main challenge is at the beginning when you're still learning how to set up. The setup and knowing how to do it the first time can be challenging.

I can recommend using it to save costs and for faster deployment, better performance, security, and easy clustering. It's easy to set up, manage, and monitor because when it goes down, it's easy to identify issues. Troubleshooting is straightforward, unlike other applications where you have to do a lot of digging to find the root cause. With this solution, you can see problems directly on your dashboards.

Public Cloud

Amazon Web Services (AWS)

For the usual use cases of Amazon EKS, we have been running different kinds of servers, such as web pages, and we have also used it to provide the SaaS solution for the end customer, delivering software as a service to the end customers. Basically, I deal with apps, SaaS applications, and websites.

We don't use Amazon EKS internally for us; we usually provide the service to others for their solutions.

The most valuable capability of Amazon EKS is managing the management portion of Kubernetes, which is the best thing that we get from Amazon EKS. Even though we have to upgrade it every six to seven months, it provides all the things required for us, so if a person knows how to install it and make use of it, that's all that's needed for using Amazon EKS.

Regarding self-healing nodes of EKS in minimizing administrative burdens for my customers, I appreciate that this feature allows nodes to try to heal themselves, which is a good feature. However, I haven't used this feature often, but having the service's ability to find and heal themselves or replicate is a good option for Amazon EKS to maintain high infrastructure uptime.

The area of Amazon EKS that could be improved is the development cycles because every six months a new version of Kubernetes is launched. Working in the infrastructure, I have found it quite difficult to keep up with infrastructure updates and new versions. Migrating the whole infrastructure from one Amazon EKS cluster to another is quite cumbersome, so if possible, version management should be made much easier than it is now, perhaps with some option to deploy code using blue-green updates. Creating a clone of the current infrastructure, updating it to the latest version, and terminating the old infrastructure would be a great enhancement.

I haven't used Amazon EKS's automated patching feature, but I believe it involves directly upgrading the AMI versions remotely or from the Amazon EKS dashboard. I understand it is a good feature, but I haven't used it yet.

I have been working with Amazon EKS for seven years in Kubernetes only, and I would say four years in Amazon EKS specifically.

My experience with the deployment and initial setup of Amazon EKS is usually straightforward. If you have the right Terraform code or the right knowledge, you can create it from the console or using Terraform or other tools; I don't find difficulties in starting a Kubernetes cluster. However, using the right principles or tools together with Amazon EKS may be challenging.

In terms of stability, Amazon EKS is pretty good. I don't encounter issues with stability if I use the right methods of deployment. For instance, using spot instances that are inexpensive can lead to downtime if not managed correctly.

My experience with customer service and technical support of AWS for Amazon EKS has been generally positive. Earlier, I was in developer support where the response time was maybe three to four hours after ticket submission, but I was able to resolve most problems with their support. I don't have any complaints.

I would rate technical support for Amazon EKS at an eight out of ten based on my experience with the developer support.

Positive

I have been using Amazon EKS for four years. In addition, I have used other solutions.

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.

Public Cloud

Amazon Web Services (AWS)

I use Amazon EKS mainly for deploying my application onto the Kubernetes infrastructure, which is provided by the underlying Amazon infrastructure.

I have many services, many applications, and many web services and web applications which are deployed using Amazon EKS across different regions in Amazon web service locations and data centers.

Other than deploying applications onto Kubernetes infrastructure using Amazon EKS, I don't have any other use cases for this tool in my current organization.

Amazon EKS has very good scalability with 100% uptime and zero latency.

Amazon EKS is the most cost-effective solution that I am using currently. If I want to reduce my downtime, I can deploy it in a multiple region architecture, which can reduce the downtime.

It is a cloud-based solution which is managed by Amazon, a global cloud services provider. I have observed very negligible issues while running my applications on Amazon EKS.

It is very pocket-friendly, cost-effective, and the setup is very simple.

If you are running a few applications that require high scalability, you can go for Amazon EKS. It is a very good tool if you want a managed Kubernetes service. It will definitely work wonders for your project.

Currently I work for a financial global giant where a millisecond latency costs around a million dollars. With Amazon EKS, I have a lot of benefits.

The only thing I feel is keeping Amazon EKS updated with the current trends and requirements of the global giants which are using this tool.

I have been using Amazon EKS for the past three years. It is very brilliant.

I have worked on several improvements, particularly regarding instances when Amazon goes down, which is the only time I see issues in Amazon EKS.

It is pretty good and pretty stable.

I have not experienced any scalability issues.

I have not had any issues with customer service.

Negative

I have not used any previous solutions.

I don't have any alternate solutions.

It is already a great tool. It is already a very good tool in the market. I would rate this product a 10 out of 10.

Public Cloud

Amazon Web Services (AWS)

I mainly use the service for competition purposes, specifically for a specific competition.

The tools we are trying to see align with R&D's use cases, and then we are going to integrate them.

It provides benefits in terms of operational efficiency.

I consider Amazon EKS to be cost-effective.

The way we are using Amazon EKS is quite good, and it is fulfilling all the purposes we wanted to use it for until now. All the tools we are using in this project are AWS tools, and we are fully satisfied.

Nothing comes to my mind right now that could be improved in Amazon EKS, and I am not facing any issues.

I joined this project later, but I have been working with AWS for more than one and a half years now.

I have not contacted AWS technical support in this project, but in previous projects, we contacted them twice regarding database and other issues. They are quite good, and because it is a build project, we received immediate support within twenty-four hours. During the call, issues were solved immediately.

Positive

I have not worked with that tool currently or previously in Germany as we were not using it at that moment.

I am currently conducting POCs.

I have about four to five AI tools, with around one month of experience so far.

This is a new initiative that has not happened before.

I do not have hands-on experiences, and I have not tried Google Gemini yet. It is just a new feature we are trying to implement with AI.

With the POC, we are trying to figure out all those things, as it has already been done as part of POC, so I do not anticipate any issues later on.

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

Amazon Web Services (AWS)

I use Amazon EKS for managing production environments. I have worked for different companies over the past three years, managing microservice applications on Amazon EKS to deploy application code to the environment, including the production environment. We use DevOps methodology to deploy these services.

The most beneficial aspect of Amazon EKS is that it helps manage the Kubernetes master node, so I don't need to maintain the master node, including tasks like upgrading. This allows me to focus on business code. If using services like Fargate, I only need to maintain my workload, simply uploading code that will be deployed to the Kubernetes cluster. This is especially beneficial for startup companies that lack the technical resources to manage the Kubernetes cluster. Furthermore, Amazon EKS allows me to utilize Kubernetes cluster-level expansion. If there’s insufficient resource on a machine, the cluster can automatically expand to add new nodes.

Although Amazon EKS is popular, there are areas for improvement. It could support more scenarios and plugins. Currently, some third-party plugins, like certain network plugins such as Weave CNI, might not be fully supported. 

I have been working with Amazon EKS for more than three years.

I haven't found any performance issues with Amazon EKS so far. To avoid potential performance issues, it is important to plan resources initially, ensuring there are enough compute resources like nodes to host applications.

Amazon EKS is very scalable, but scaling can sometimes cause trouble. When Amazon EKS scales up or down, there might be occasional intermediate pod interruptions, though it's rare.

I have escalated some questions to AWS tech support before. I once faced a random issue where a pod abruptly shut down and restarted. Upon escalation, AWS helped me find the root cause. Overall, I would rate AWS tech support an eight out of ten.

Positive

I have experience with Azure AKS and some exposure to Google GKE. However, I mostly have experience with Amazon EKS.

When I first set up Amazon EKS, I faced challenges because there are different setup methods. Using the console does not align well with DevOps. It is better to use EKS CTL or Terraform's IAC tools. Configuring role permission policies is the most challenging part, ensuring Amazon EKS has access to different services or databases.

I have experience with Azure AKS and some exposure to Google GKE.

I would recommend Amazon EKS for large companies, especially banks, due to AWS's extended support for Amazon EKS, its availability, and reliability. Amazon EKS offers a strong solution as part of a full suite, but it should be integrated with services like Lambda for a complete solution. On a scale of one to ten, I rate Amazon EKS an eight because there is still room for improvement. The overall product rating is eight out of ten.

Public Cloud

Amazon Web Services (AWS)

I use Amazon EKS for one of my customers when I am an independent contractor. They do video recording for events such as weddings, advertisements, and other occasions. They wanted to stream their content, and I advised them to use Amazon EKS as a good solution so they can easily ingest the raw materials, process it, do all the cuts using specific video software, and then publish it wherever they need.

The ease of implementation and integration was accomplished by writing some small scripts. I implemented workflows for data ingestion, sending it for cuts, and then directing it to the presentation layer. The simplicity of it was key.

The automated patching feature for the Kubernetes clusters provided valuable benefits through ease of maintenance and simplification of maintenance. I don't have to manually monitor or create any additional services for monitoring the patches; it's just there and does the work automatically.

From my perspective, integrating existing applications into a single workflow is beneficial for application development and application integration.

The workflows were straightforward, collecting data from raw recordings from cameras, putting them on cloud storage, ingesting them into video editing software, and going to a CDN for publishing.

About a year and a half ago, the cost was somewhat high. Though I wasn't directly affected as my customer paid for it, they complained about the billing. If they could reduce the price, that would probably attract more customers, especially from this industry, as they are rather small companies with limited budgets for such tooling.

I have been working with Amazon EKS for about a year and a half, with my first notes dating from March 2024.

I escalated a couple of cases to AWS support. I have mixed feelings about this as they were quite helpful, but the response times were quite long. It took them about five business days to get a response to my question, but when they replied, the response was very valuable and helped me.

I didn't notice any crashes, slowness, or performance issues with the Amazon EKS product. My client could have potentially experienced such issues while using it, but they never reported any complaints, so I don't believe there were any issues.

I would rate the tech support around seven or eight on a scale of one to ten.

Positive

I worked with container services about a year ago as part of my project at that time. I enjoyed using AKS, but I think its equivalent in AWS is better; it's more mature and easier to implement than AKS on Azure.

The best feature I found in Amazon EKS is ease of implementation. I'm not very knowledgeable about video software and had to learn it quickly for this specific project, and I found it very easy to implement. It probably took me a couple of hours to really understand it and learn how to use videos, and it was probably the easiest of all the solutions that I tried.

I use the DevOps server as software as a service on Azure. I didn't need to set any server for that; it was just there. I added it to my dashboard and started using it.

In terms of cost savings, time savings, and efficiency improvements, I've definitely seen returns on investment. Considering my rate and the couple of hours spent, rough calculations show around 30% return on investment.

The majority of my time setup cost was very affordable, taking just two hours. It was easy as I didn't have to worry about setting all the infrastructure underneath, just using what's there. This saved my time, allowing me to complete the project within several hours instead of days or weeks.

When I evaluated several solutions, Amazon EKS looked more intuitive to learn. I was prototyping for two hours each, and with Amazon EKS, I had this raw prototype running after around two hours. With other services, after two or three hours, I was still in the middle of my work with no visible effect, so that was the benefit.

I am working with a set of tools within the Azure toolbox. Azure is a huge collection of services with over 100 of them. I use virtual machines, Azure Functions for serverless processing, especially for creating APIs that do automated tasks. Additionally, I use SQL Server database and infrastructure as code, creating using Terraform, creating virtual private networks, setting up firewall rules to increase the security of my customer's solution.

I give Amazon EKS a rating of 8 out of 10.

Amazon Web Services (AWS)