Terraform code for Leverage Reference Architecture for AWS, designed under optimal configs for the most popular modern web and mobile applications needs.
This feature will be useful for day 2 operations for Amazon EKS. It will help ensure that EKS clusters follow the best practices for security, reliability, cluster autoscaling, running Windows containers, networking, and scalability, among others. By incorporating the tool example into the Leverage Reference Architecture for AWS repository, the community will be able to quickly iterate and provide timely and effective recommendations for EKS clusters.
Describe Ideal Solution
The ideal solution is to incorporate the https://github.com/aws-samples/hardeneks tool example guide into the Leverage Reference Architecture for AWS repository, or probably at https://github.com/binbashar/le-ref-architecture-doc (if better). The tool should be run on a case-by-case basis for each EKS cluster to validate that it follows the EKS Best Practices guides. The tool should also propose improvements based on the best practices guides.
Alternatives Considered
Other tools for EKS cluster validation were considered, but https://github.com/aws-samples/hardeneks was chosen because it is specifically designed to check if an EKS cluster follows the EKS Best Practices. Additionally, the tool is open source and officially maintained by AWS.
Additional Context
The EKS Best Practices guides can be found at https://aws.github.io/aws-eks-best-practices/. The primary goal of this project is to offer a set of best practices for day 2 operations for Amazon EKS. The guides cover topics such as security, reliability, cluster autoscaling, running Windows containers, networking, and scalability. Incorporating the https://github.com/aws-samples/hardeneks tool into the Leverage Reference Architecture for AWS repository will help ensure that EKS clusters follow these best practices.
Describe the Feature
Add a reference tool to validate best practices and propose improvements for the implementation of EKS clusters.
Expected Behavior
The tool to be added is https://github.com/aws-samples/hardeneks. Its purpose is to run checks to see if an EKS cluster follows EKS Best Practices. The goal is to validate the implementation and propose improvements based on the best practices guides (https://aws.github.io/aws-eks-best-practices/).
Use Case
This feature will be useful for day 2 operations for Amazon EKS. It will help ensure that EKS clusters follow the best practices for security, reliability, cluster autoscaling, running Windows containers, networking, and scalability, among others. By incorporating the tool example into the Leverage Reference Architecture for AWS repository, the community will be able to quickly iterate and provide timely and effective recommendations for EKS clusters.
Describe Ideal Solution
The ideal solution is to incorporate the https://github.com/aws-samples/hardeneks tool example guide into the Leverage Reference Architecture for AWS repository, or probably at https://github.com/binbashar/le-ref-architecture-doc (if better). The tool should be run on a case-by-case basis for each EKS cluster to validate that it follows the EKS Best Practices guides. The tool should also propose improvements based on the best practices guides.
Alternatives Considered
Other tools for EKS cluster validation were considered, but https://github.com/aws-samples/hardeneks was chosen because it is specifically designed to check if an EKS cluster follows the EKS Best Practices. Additionally, the tool is open source and officially maintained by AWS.
Additional Context
The EKS Best Practices guides can be found at https://aws.github.io/aws-eks-best-practices/. The primary goal of this project is to offer a set of best practices for day 2 operations for Amazon EKS. The guides cover topics such as security, reliability, cluster autoscaling, running Windows containers, networking, and scalability. Incorporating the https://github.com/aws-samples/hardeneks tool into the Leverage Reference Architecture for AWS repository will help ensure that EKS clusters follow these best practices.