Improved documentation in README.md.

Author: BSick7

CHANGELOG.md

@@ -1,2 +1,5 @@
+# 0.1.1 (Mar 24, 2026)
+* Improved documentation in README.md.
+
 # 0.1.0 (Mar 10, 2026)
 * Initial release

README.md

@@ -1,16 +1,40 @@
-# aws-eks
+# aws-eks-auto
 
-This is a nullstone module to create an AWS-managed Kubernetes Cluster using EKS and Fargate.
-This module comes with a `deployers` IAM group that has privileges to perform deployments.
+Creates a Kubernetes cluster in Auto mode that uses AWS-managed node groups.
 
-## Security & Compliance
+## When to use?
 
-Security scanning is graciously provided by Bridgecrew. Bridgecrew is the leading fully hosted, cloud-native solution providing continuous Terraform security and compliance.
+### When Auto Mode is GREAT
+- SaaS workloads
+- stateless services
+- CI runners
+- internal platforms
+- preview environments (👀 very relevant to you)
+- cost optimization focus
+- teams without deep k8s infra skills
 
-[![Infrastructure Security](https://www.bridgecrew.cloud/badges/github/nullstone-modules/aws-fargate/general)](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=nullstone-modules%2Faws-fargate&benchmark=INFRASTRUCTURE+SECURITY)
-[![CIS AWS V1.3](https://www.bridgecrew.cloud/badges/github/nullstone-modules/aws-fargate/cis_aws_13)](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=nullstone-modules%2Faws-fargate&benchmark=CIS+AWS+V1.3)
-[![PCI-DSS V3.2](https://www.bridgecrew.cloud/badges/github/nullstone-modules/aws-fargate/pci)](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=nullstone-modules%2Faws-fargate&benchmark=PCI-DSS+V3.2)
-[![NIST-800-53](https://www.bridgecrew.cloud/badges/github/nullstone-modules/aws-fargate/nist)](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=nullstone-modules%2Faws-fargate&benchmark=NIST-800-53)
-[![ISO27001](https://www.bridgecrew.cloud/badges/github/nullstone-modules/aws-fargate/iso)](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=nullstone-modules%2Faws-fargate&benchmark=ISO27001)
-[![SOC2](https://www.bridgecrew.cloud/badges/github/nullstone-modules/aws-fargate/soc2)](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=nullstone-modules%2Faws-fargate&benchmark=SOC2)
-[![HIPAA](https://www.bridgecrew.cloud/badges/github/nullstone-modules/aws-fargate/hipaa)](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=nullstone-modules%2Faws-fargate&benchmark=HIPAA)
+### When Auto Mode is NOT ideal
+- custom networking
+- heavy DaemonSet reliance
+- GPU tuning
+- special storage drivers
+- low-level performance control
+- platform engineering teams wanting full control
+- highly predictable infra topology needs
+
+## Included Addons
+
+AWS automatically manages the following addons:
+- VPC CNI
+- CoreDNS
+- kube-proxy
+- Pod Identity Agent
+- metrics server
+- networking dataplane components
+
+## Limitations
+
+In auto mode, AWS manages a fleet of nodes which prevents you from performing various operations:
+1. You cannot run DaemonSets.
+2. You cannot SSH into nodes.
+3. You cannot optimize pod scheduling; AWS optimizes this.