// the find
aws-controllers-k8s/community
AWS Controllers for Kubernetes (ACK) is a project enabling you to manage AWS services from Kubernetes
ACK lets you manage AWS resources (RDS, S3, SQS, Lambda, etc.) using Kubernetes CRDs and controllers, so you can define your infrastructure in the same manifests as your application. It is for teams already running on EKS who want to avoid Terraform or CloudFormation as a separate provisioning layer. This repo is the community/documentation hub; the actual controllers live in per-service repos.
The code-generation approach is architecturally sound — a single code generator produces all service controllers from the AWS API models, which means new services get consistent behavior rather than hand-rolled quirks. Cross-account resource management via IRSA is first-class, not bolted on. The drift recovery controller actively reconciles observed vs. desired state on a configurable schedule, so you are not relying purely on event-driven reconciliation. The adopted-resource feature lets you import existing AWS resources into ACK management without recreating them.
Controller maturity is wildly uneven — some services are GA while others are still in Preview and explicitly unsupported for production, and there is no obvious signal in the UX when you are about to create something with a Preview controller. The generated controllers have known gaps around complex update semantics: many AWS APIs distinguish create-only fields from mutable fields, and the code generator does not always get that right, which can cause your reconciler to attempt forbidden updates and get stuck. The community repo itself contains no runnable code, which is confusing — you have to find the right per-service repo and the star count here does not reflect how active any individual controller actually is. Field export (getting resource outputs like RDS endpoint back into Kubernetes Secrets) works but the UX is awkward YAML ceremony that most teams end up working around with external-secrets instead.