We've Moved to the AWS Docs! 🚀
This content has been updated and relocated to improve your experience. Please visit our new site for the latest version: AWS EKS Best Practices Guide on the AWS Docs
Bookmarks and links will continue to work, but we recommend updating them for faster access in the future.
Introduction¶
Welcome to the EKS Best Practices Guides. The primary goal of this project is to offer a set of best practices for day 2 operations for Amazon EKS. We elected to publish this guidance to GitHub so we could iterate quickly, provide timely and effective recommendations for variety of concerns, and easily incorporate suggestions from the broader community.
We currently have published guides for the following topics:
- Best Practices for Security
- Best Practices for Reliability
- Best Practices for Cluster Autoscaling: karpenter, cluster-autoscaler, EKS Auto Mode
- Best Practices for Networking
- Best Practices for Scalability
- Best Practices for Cluster Upgrades
- Best Practices for Cost Optimization
- Best Practices for Running Windows Containers
We also open sourced a Python based CLI (Command Line Interface) called hardeneks to check some of the recommendations from this guide.
In the future we will be publishing best practices guidance for performance, cost optimization, and operational excellence.
Related guides¶
In addition to the EKS User Guide, AWS has published several other guides that may help you with your implementation of EKS.
- EMR Containers Best Practices Guides
- Data on EKS
- AWS Observability Best Practices
- Amazon EKS Blueprints for Terraform
- Amazon EKS Blueprints Quick Start
Contributing¶
We encourage you to contribute to these guides. If you have implemented a practice that has proven to be effective, please share it with us by opening an issue or a pull request. Similarly, if you discover an error or flaw in the guidance we've already published, please submit a PR to correct it. The guidelines for submitting PRs can be found in our Contributing Guidelines.