Sold by: Center for Internet Security
Deployed on AWS
AWS Free Tier
This product has charges associated with the pre-built hardening to the CIS Benchmarks™ and recurring maintenance. The CIS Hardened Images® are hardened in accordance with the associated CIS Benchmarks, an industry best practice for secure configuration. Reduce cost, time, and risk by building your AWS solution with CIS AMIs.
4.2
Overview
The CIS Hardened Image Level 1 on Amazon EKS-Optimized Amazon Linux 2 is a pre-configured image built by the Center for Internet Security (CIS®) for use on Amazon Elastic Compute Cloud (Amazon EC2) and optimized for use with Amazon Elastic Container Service for Kubernetes (Amazon EKS). It is a pre-configured, security-hardened image that aligns with the robust security recommendations, the CIS Benchmarks, making it easier for organizations to meet regulatory requirements. Not only is this image pre-hardened to the CIS Benchmarks guidance, but it is also patched monthly in alignment with the updates from the software vendor. Key Benefits
Highlights
- Hardened according to a Level 1 CIS Benchmark that is developed in a consensus-based process and that is accepted by government, business, industry, and academia.
- Helps with compliance to PCI DSS, FedRAMP, DoD Cloud Computing SRG, FISMA, select NIST publications, and more.
- Pre-configured to align with industry best practices that are developed and supported by CIS, this image has hardened account and local policies, firewall configuration, and computer-based and user-based administrative templates.
Details
Sold by
Categories
Delivery method
Delivery option
64-bit (x86) Amazon Machine Image (AMI)
Latest version
Operating system
AmazonLinux 2
Deployed on AWS
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide
Gain valuable insights from real users who purchased this product, powered by PeerSpot.
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time. Alternatively, you can pay upfront for a contract, which typically covers your anticipated usage for the contract duration. Any usage beyond contract will incur additional usage-based costs.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
If you are an AWS Free Tier customer with a free plan, you are eligible to subscribe to this offer. You can use free credits to cover the cost of eligible AWS infrastructure. See AWS Free Tier for more details. If you created an AWS account before July 15th, 2025, and qualify for the Legacy AWS Free Tier, Amazon EC2 charges for Micro instances are free for up to 750 hours per month. See Legacy AWS Free Tier for more details.
Dimension | Cost/hour |
|---|---|
t3.medium Recommended | $0.022 |
t2.micro | $0.02 |
t3.micro | $0.022 |
r5b.24xlarge | $0.06 |
gr6.4xlarge | $0.035 |
r5a.12xlarge | $0.055 |
r6a.xlarge | $0.024 |
m7i-flex.8xlarge | $0.05 |
r6id.24xlarge | $0.06 |
r5dn.2xlarge | $0.026 |
Vendor refund policy
Refunds through AWS are not available at this time. You will only be billed for actual time of instance use. As with all CIS security products, our aim is always 100 percent customer/member satisfaction.
Custom pricing options
Request a private offer to receive a custom quote.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
NA
Additional details
Usage instructions
No sensitive information supplied by customers will be stored outside this instance. No data encryption configuration is applicable to this instance. You can encrypt the instance EBS volume per standard EC2 processes. No programmatic system credentials and cryptographic keys are used by this instance. Launch the instance via the AWS Marketplace or EC2 console. Navigate to your Amazon EC2 console and verify that you're in the correct region. Choose instance and select your launched instance. Select the server to display your metadata page and choose the Status checks tab at the bottom of the page to review if your status checks passed or failed. Connect using SSH. Use "ec2-user" as the username. Immediately apply latest security updates to the instance.
Support
Vendor support
Questions, feedback, and support accessing CIS-developed AMIs is provided by contacting
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Updated weekly
By Center for Internet Security
By Canonical Group Limited
By Arara Solutions
Top
25
In Compliance and Auditing
Sentiment is AI generated from actual customer reviews on AWS and G2
Functionality
Ease of use
Customer service
Cost effectiveness
Positive reviews
Mixed reviews
Negative reviews
AI generated from product descriptions
Security Hardening
Pre-configured image hardened according to CIS Benchmarks Level 1 security recommendations
Configuration Assessment
Includes CIS Configuration Assessment Tool (CIS-CAT Pro) reports for verifying hardening compliance
Benchmark Alignment
Follows industry-recognized security guidance developed through consensus-based process
System Integrity
Applies security configurations to account policies, firewall settings, and administrative templates without modifying base image packages
Compliance Documentation
Provides detailed hardening reports including pre and post-hardening package lists and configuration exceptions
Cryptographic Compliance
FIPS 140-2 certified kernel and cryptographic modules with out-of-the-box compliance
Security Patch Coverage
Comprehensive security updates for over 23,000 open source packages across Ubuntu Universe repository
Compliance Hardening
Integrated hardening profiles from CIS and DISA-STIG security implementation guidelines
Kernel Security
FIPS-certified kernel with ongoing security updates for cryptographic components
Security Tooling
Ubuntu Security Guide (USG) for automated compliance and security configuration management
Security Hardening
"Configured with Security Technical Implementation Guides (STIG) Benchmark High to enhance system security posture"
Operating System Compatibility
"Optimized Amazon Linux 2 distribution configured for compatibility with Amazon Elastic MapReduce (EMR)"
Compliance Standard
"Meets Defense Information System Agency (DISA) configuration standards for system hardening"
Security Configuration
"Implements advanced security settings to improve overall system protection"
Platform Optimization
"Pre-configured Linux image with specialized security and performance configurations"
Standard contract
No
No
Customer reviews
reviewer2795433
Running secure containerized web apps has been simplified and integrates tightly with cloud tools
Reviewed on Jan 15, 2026
Review from a verified AWS customer
What is our primary use case?
Amazon EKS 's main use case is using compute in a highly containerized format. Building and running applications is my primary use case for Amazon EKS .
I currently use Amazon EKS to run a web application. I have my own website which I host on Amazon EKS.
Currently, I use Amazon EKS to host a web application, but Amazon EKS is so versatile. I have used it previously to host a whole host of different applications.
What is most valuable?
One of the features I really appreciate about Amazon EKS is its ability to integrate with other AWS tooling. That is very useful because it is part of the wider Amazon ecosystem. For example, if you wanted to grant access to a specific pod within Kubernetes , you could use Amazon EKS to provision a service account for that pod to interact directly with a bucket. You would not get this type of benefit if you used Kubernetes out of the box which was not running on an Amazon service. The ability to integrate with other Amazon tooling and do it at a very granular level is something I value.
From a security perspective, Amazon EKS is very strong. That granularity allows for specific pods to have access to specific buckets or specific EC2 instances. It allows for the principle of least privilege at a very granular level, which improves the security of using the tool.
Amazon EKS allows me to use applications and deploy them in a specified format and to scale that across huge numbers. Because you can deploy Amazon EKS via Terraform or other infrastructure as code tools, it allows for a repeatable architecture, which is brilliant because once it is developed, it is very simple to then deploy further versions for potentially different customers or different versions of the same application.
What needs improvement?
One limitation I have found with using Amazon EKS is that there is a very big learning curve. It is very complicated to use the tool. I have used Google's GKE which offers an easier framework because they offer managed clusters, which are called Autopilot clusters. With that, a lot of the management is abstracted away and managed by Google. Amazon does not have the equivalent of that, so you would have to manage everything yourself. In some scenarios you would want to do this because you might want that level of granular control. But if you are running a proof of concept or developing in a very quick way, it becomes very difficult and time-consuming to get it initially running.
Another limitation I have found is the management overhead of upgrading Amazon EKS. Because Kubernetes has frequent updates, you have to manually trigger those in AWS , which can be quite time-consuming, especially if you are managing many clusters. Amazon could potentially make it easier by automatically triggering upgrades, but it is definitely a high toil activity, especially for smaller teams.
For how long have I used the solution?
I have been using Amazon EKS for around four years.
What do I think about the stability of the solution?
Amazon EKS is very stable. You can set up your clusters to have however many nodes you want, which allows for greater stability when users are using it. You are able to upgrade whenever a new upgrade comes out.
What do I think about the scalability of the solution?
Amazon EKS's scalability is brilliant. You can easily scale from zero nodes all the way up to the tens of thousands, probably even higher. There would not really be a bottleneck in terms of scalability. You can have it however you wish.
How are customer service and support?
Customer support for Amazon EKS is brilliant. It uses AWS's customer support which could be as quick as probably five-minute response time or 15-minute response time. Whenever I have contacted them, I get responses every single time, same day, and Amazon's expertise is immense. There are no complaints there.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have previously used GKE from GCP. You would only really use that if your other workloads are running within Google Cloud as well. If your workloads are running in AWS, using Amazon EKS is better because it allows for better linkages between different products within that cloud platform.
How was the initial setup?
In terms of deployment speed, if Terraform files are configured to deploy on Amazon EKS and they are written in a very efficient way, deployment could be as quick as five minutes. Compared to deploying on a traditional virtual machine in a data center, which would be hours, that is a big time saving. You can very easily save over 50% of the time if you are deploying on Amazon EKS compared to in a traditional manner.
What was our ROI?
Return on investment with Amazon EKS is positive, because it allows applications to be hosted. In terms of money saved, if a team was to go from not using autoscaling to using autoscaling in terms of how much user traffic is actually generated, teams could easily save over 30% of costs just from that one tool being enabled alone.
What's my experience with pricing, setup cost, and licensing?
Pricing for Amazon EKS is quite good, because you can choose the instances which are running under the hood. If you wanted to use smaller machine types, you can control your cost quite well. You are also only paying when those machines are up. You could configure your nodes to scale down massively when you do not need them up all the time. It is very cost-efficient due to its flexibility.
Which other solutions did I evaluate?
I did not really evaluate other options before choosing Amazon EKS, because if workloads are run on AWS, you would only really use Amazon EKS if you wanted a managed Kubernetes service. Amazon does not offer another service which would compete with that.
What other advice do I have?
Overall, Amazon EKS is a very good tool to use and it is commonly used in the industry. However, GKE is easier to use and some of the management is abstracted away, which is not the case with Amazon, so that is one drawback. The need to upgrade yourself as well is another limitation. I believe with GKE Autopilot, you do not have to do that because Google manages it under the hood. The fact that it is not as automated as similar Kubernetes products on the market is what takes off those last two points.
I did not purchase Amazon EKS through the AWS Marketplace . I bought it directly through Amazon on their AWS platform.
I would recommend using Amazon EKS if your workloads are running on AWS. If your workloads are running on Azure or GCP, you probably would not want to use it just because you would get better linkages if you were using the cloud platform's own Kubernetes service. I personally prefer GKE because of the Autopilot feature, but Amazon EKS is a brilliant tool if you are already on Amazon's platform. I have provided a review rating of 8 out of 10 for this product.
reviewer2796066
High availability has boosted our AI reporting workflows but navigation and pricing still need work
Reviewed on Jan 12, 2026
Review from a verified AWS customer
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working in my current field for three years.
What do I think about the stability of the solution?
In my experience, Amazon EKS is stable.
What do I think about the scalability of the solution?
The scalability of Amazon EKS is good.
How are customer service and support?
The customer support of Amazon EKS is good. I would rate the customer support on a scale of one to ten as a seven.
How would you rate customer service and support?
Positive
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
reviewer2787357
Modern microservices have delivered faster deployments and stronger security for our teams
Reviewed on Jan 09, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Amazon EKS is to run and manage containerized applications at scale with high availability, security, and automated deployments.
I am using Amazon EKS to run microservices in production. I host stateless backend APIs and web services, and each service runs in Docker containers, scaling horizontally based on traffic. I chose Amazon EKS because of Kubernetes native scaling, and it provides self-healing and rolling updates. I am also using Amazon EKS for continuous deployment of containers, deploying Docker images built in CI, using Helm and manifests for version releases and supporting rolling, blue-green, and canary deployments. Security and access control are also major reasons for using it, with IAM integrated authentication, network policies, and pod-level isolation, which Amazon EKS provides. It also offers secret management integrations and scalable infrastructure management, providing auto-scaling worker nodes that scale from a few pods to hundreds without redesign.
The main use case for Amazon EKS is running and scaling production-grade, containerized microservices with automated deployments, high availability, and strong security on AWS .
What is most valuable?
The best feature Amazon EKS offers, especially for production workloads, is its fully managed Kubernetes control plane, where AWS manages the Kubernetes master, ETCD, upgrades, and HA. The control plane runs across multiple AZs, providing high availability and resilience, with multi-AZ control plane and workloads by default, along with automatic pod restarts and self-healing. Native AWS IAM integration is also present, providing fine-grained access using IAM roles and policies, and IAM roles for service accounts. There are other features, including deep AWS ecosystem integrations, a standard Kubernetes experience, and strong security and compliance, upgrade, and version control, which I would say are great features. If I have to name the top three features or the biggest impacts, they would be managed control plane, IAM plus IRSA security model, and auto-scaling with EC2 or Carpenter.
Amazon EKS has had a strong positive impact on our organization by improving key aspects that matter to every organization, such as reliability, scalability, deployment speed, and operational efficiency for containerized workloads.
What needs improvement?
There are one or two areas for improvement that I can suggest, starting with operational capacity. There is a steep learning curve for teams new to Kubernetes and many moving parts like VPC, CNI, IAM, and add-ons and node groups. Improvements could include better out-of-the-box defaults and a simplified setup and management workflow. Moreover, observability out-of-the-box could be enhanced, as monitoring and logging require multiple add-ons, which should not be the case. Additionally, there is no single unified observability experience, so better built-in metrics, logs, and tracing, along with a native dashboard without heavy setup, would be beneficial.
For how long have I used the solution?
I have been using Amazon EKS for more than four years.
What do I think about the stability of the solution?
Amazon EKS is quite stable.
What do I think about the scalability of the solution?
The scalability of Amazon EKS has been excellent and production-grade in my experience, as it scales both application and infrastructure reliability with minimal manual interventions. The practices I have analyzed in Amazon EKS include pod-level scaling, node-level scaling, and traffic and load scaling, all of which have been great.
How are customer service and support?
Customer support has been great; I have reached out a few times, and the responses have been very quick, ensuring that any issues are resolved as soon as possible. I would rate the customer support a 10.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have not used a different solution; I am using Amazon EKS only.
How was the initial setup?
Our experience with pricing felt reasonable for production clusters given the managed control plane and high availability, although the fixed cost for smaller non-production clusters felt relatively high. Amazon EKS charges a fixed fee per cluster, currently per hour, which applies regardless of workload size. Our experience shows that using auto-scaling and right-sizing helps control costs, and combining on-demand, spot instances, and scaling policies reduced compute spending. In terms of setup, our initial setup required moderate engineering effort, especially for teams new to Kubernetes, but utilizing Terraform and AWS best practices significantly reduced setup time and errors.
What was our ROI?
We have seen a clear and measurable return on investment from using Amazon EKS, both in cost efficiency and operational productivity. Improvements in deployment speed and MTTR are evident, alongside infrastructure cost optimizations. Developer productivity and onboarding have also improved, leading to 60 to 70% faster onboarding and faster time to market. Additionally, engineering costs have decreased because processes that were previously manual are now automated, reducing the number of engineers needed to handle those tasks.
Which other solutions did I evaluate?
We evaluated some other applications and services, including Amazon ECS , which is Elastic Container Service, self-managed Kubernetes on EC2 , and Docker Swarm. However, we decided to move to Amazon EKS because it proved to be more reliable and scalable than the others.
What other advice do I have?
I share every bit of advice that I feel is valuable regarding scalability at both the application and infrastructure levels, along with all the features that Amazon EKS offers. I share the positive impacts we have seen in our organization and team, including improved reliability and uptime, faster and safer deployments, and scalability without needing re-architecture. I provide metrics highlighting how it has improved our team's efforts and reduced manual tasks.
Amazon EKS has positively impacted deployment speed with a 65 to 75% reduction in deployment time. Before Amazon EKS, it took 30 to 60 minutes per deployment, and now it takes only 10 to 15 minutes. The rollback and recovery MTTR has also greatly improved, with a 75 to 85% reduction in MTTR. Earlier, it took up to 45 minutes for manual rollback, and now it takes only 5 to 10 minutes with automated rollback. We have seen a reduction in production incidents, specifically outages caused by configuration drift and manual deployments, as using Amazon EKS allows us to perform it automatically. This has resulted in 50 to 60% fewer release-related incidents. The scalability and traffic handling are also great, as it can handle two to three times traffic spikes without manual intervention, with auto-scaling triggered within minutes, leading to zero downtime during peak loads. Operational efficiency is also improved, with less time managing clusters and fewer failures, showing a 30 to 40% reduction in Kubernetes operational effort. After adopting Amazon EKS, we have reduced deployment time by 70%, MTTR by over 75%, and release-related incidents by around 55 to 60%, significantly improving scalability and operational efficiency. Overall, it has been a great experience, and I find it very useful and helpful for my team and organization.
Amazon EKS is a great service to use or implement in an organization or team, and I would rate this review as an 8 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)
Deva Rugved
Managed Kubernetes workflows have streamlined deployments and improved our cloud automation
Reviewed on Jan 08, 2026
Review from a verified AWS customer
What is our primary use case?
I used Amazon EKS throughout my internship while working on Docker-based deployments, Kubernetes orchestration, and cloud infrastructure tasks at Cognizant.
I used Amazon EKS when working as an intern at Cognizant, where it was used to deploy, manage, and scale containerized web applications. Our workflow started with building Docker images, storing them in Amazon ECR , and deploying them to Amazon EKS clusters running on EC2 worker nodes with CI/CD pipelines. We used many tools; for example, Jenkins was part of our CI/CD pipelines that automated the build and deployment process.
Additionally, I worked on application deployments, updating Kubernetes manifests, managing pods and services, and verifying application health. Amazon EKS acted as a central platform that connected Docker , AWS infrastructure, and DevOps automation into one consistent system.
I used Amazon EKS during my internship at Cognizant as part of a cloud and DevOps-focused environment, where it served as the core Kubernetes platform to run containerized applications built with Docker, deployed through CI/CD pipelines, and hosted on AWS infrastructure. We deployed numerous web applications, and we wanted to learn Amazon EKS through dummy projects with dummy web interfaces. Beyond dummy projects, we also deployed some client websites into the Kubernetes environment and managed traffic, although I cannot name the clients.
Amazon EKS is an excellent choice for organizations already invested in AWS. I recommend having a solid foundation in Docker, Kubernetes basics, and AWS core services before implementing Amazon EKS. Using infrastructure-as-code tools and following AWS best practices can significantly improve maintainability and security. Amazon EKS is particularly strong for enterprise environments and microservice-based architectures.
Amazon EKS is ideal for teams already using Docker, CI/CD, and AWS infrastructure, which our team was already utilizing. I strongly recommend learning Kubernetes fundamentals and AWS networking, containers, and security before using Amazon EKS in production, as it positively impacted our organization by making it easy to connect all our existing AWS services.
I deployed Docker applications to Amazon EKS using CI/CD pipelines, integrating with EC2 , ECR, IAM , and automated workflows.
What is most valuable?
The most valuable feature of Amazon EKS is the managed Kubernetes control plane, which allows teams to focus on DevOps and application workflow instead of cluster maintenance. Another major benefit is how naturally Amazon EKS fits into the AWS ecosystem, integrating with EC2 for compute, IAM for access control, and Amazon ECR for container images. CloudWatch for monitoring creates a complete DevOps pipeline. The self-healing nature of Kubernetes combined with AWS scalability makes the environment reliable and suitable for real-world workloads.
The most promising feature, which I prefer the most, is its integration with all the AWS services, including EC2, IAM , VPC, ECR, and CloudWatch, making it a key part of my workflow.
Amazon EKS works very well with Docker-based container workflows; it is highly scalable and self-healing, complemented by its rolling update capabilities.
What needs improvement?
There are some drawbacks regarding Amazon EKS; pricing can increase as clusters and workloads scale, and there is an initial configuration learning curve. A beginner has to learn about IAM networking and cluster setup, plus improved built-in cost visibility and simplified monitoring tools could be beneficial.
Pricing can be improved, especially for small teams or landing projects, and the initial setup, as well as understanding IAM networking and cluster configuration, can be complex for beginners; improving this would enhance the experience. Troubleshooting sometimes requires deeper AWS and Kubernetes knowledge, which also could use improvement.
What do I think about the stability of the solution?
Amazon EKS is very stable; during my usage, the clusters remained consistently available and workloads ran reliably. The self-healing capabilities of Kubernetes, combined with AWS managed infrastructure, help ensure minimal disruption to running applications.
What do I think about the scalability of the solution?
Amazon EKS is highly scalable; it supports horizontal scaling of pods and seamless scaling of worker nodes. It features AWS auto-scaling for vertical scaling, making it suitable for handling varying workloads and preparing the environment for real-world production demands.
How are customer service and support?
Support and documentation from AWS are very strong, with extensively available official documentation, and AWS support channels are very kind and responsive. Most issues can be resolved through AWS knowledge bases, documentation, and our organizational support teams.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Previously, I used open-source Kubernetes as a normal Kubernetes solution. I wanted to switch to Amazon EKS because Amazon EKS connects with numerous AWS services, making it easier to deploy my applications than using open-source Kubernetes.
How was the initial setup?
The initial setup is moderately complex; creating clusters, configuring IAM roles, setting up the network, and connecting with the worker nodes requires careful planning. However, once the environment is configured, ongoing operations such as deployment, updates, and scaling are smooth and efficient.
What was our ROI?
Time is definitely saved because Amazon EKS provides automation with CI/CD pipelines, allowing us to simply monitor it, and if there is any fault, we know immediately in the pipeline. Regarding the need for fewer employees, I do not think that will happen since only a few employees will know about Amazon EKS deployments in the cloud, so some knowledge is necessary. We can see a return on investment; we can save a lot of money by using Amazon EKS as it is directly connected with all AWS services and can be integrated with coding storage options such as GitHub and GitLab .
Which other solutions did I evaluate?
I did not evaluate many options; I evaluated some, specifically open-source Kubernetes, which I thought would be more difficult than Amazon EKS. Therefore, I chose Amazon EKS.
What other advice do I have?
The benefits that I observed after adopting Amazon EKS are improved deployment speed and reliability, while resource usage remains the same, but we can handle a larger amount of traffic and application deployments without any issues. The user interface is very great, providing clarity on where the fault or error lies while deploying our application. I would rate this product nine out of ten.
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)
Vicente Gazola
Critical microservices have been managed reliably and support secure, flexible operations
Reviewed on Dec 22, 2025
Review from a verified AWS customer
What is our primary use case?
My main use case for Amazon EKS is for implementation and sustainable services and microservice application on a critical structure and services deployment.
On our application, we have more than 20 services and microservices such as authentication, login, account management, a notification service, and a billing service, which all work together to structure a heavy, useful application.
What is most valuable?
The best features Amazon EKS offers are scalability and deployment control, the ingress configuration regarding path pattern and host header to get all the services and microservices, and the HPA configuration.
The biggest difference, or the most important aspect to me, is the scalability, because you can easily scale any service or microservice to handle security during high changes in connection flow, and it is useful for the application and helps day-to-day by giving us reliability and stability so we can perform all maintenance and deployment of our system.
Reliability is a very important thing. Security and operational consistency are very important aspects, and the flexibility offered in node management and network options is also valuable. Amazon EKS is a service that is reliable and scalable, and it gives us a solid and dependable solution.
What needs improvement?
I think sometimes the documentation is not so clear and not so fast to provide more in-depth instruction and examples of bigger and critical implementations, so some difficulties for us sometimes take a lot of time to understand, test, and to put into production with security and guarantees.
For how long have I used the solution?
I have been using Amazon EKS for almost five years now.
What other advice do I have?
I advise doing a POC first and getting all the details, testing, and having a very good alignment between DevOps and development departments, and prepare all the CDN and how the connections get into your cluster, and how you configure your ingress and how to prepare every service or microservice to receive that with secure and optimized code, process, and communication with other resources. I would rate this product an 8.
Which deployment model are you using for this solution?
Private Cloud