AWS Controllers for Kubernetes vs OpenTofu

AWS Controllers for Kubernetes (ACK) lets Kubernetes users define AWS resources with Kubernetes custom resources. It periodically compares desired and actual AWS state and corrects drift. Documentation lists 74 service controllers, including S3, RDS, Lambda and DynamoDB. ACK supports declarative, version-controlled infrastructure alongside applications, across AWS accounts and regions. Read-only resources and read-only adoption support migration from other infrastructure-as-code tools. EKS users can install managed EKS Capabilities, where AWS handles controller installation and upgrades with automatic updates, auto-scaling and auto-tuning. Self-managed Helm installation runs on EKS, GKE, AKS, on-premises clusters and local environments, providing version and configuration control. AWS IAM authorizes controller access. Self-managed ACK costs nothing for Helm installation on Kubernetes 1.20+ on any Kubernetes cluster. EKS Capability pricing is hourly, with a base rate per enabled capability plus usage charges for each ACK resource managed.

OpenTofu is a free infrastructure as code tool for defining cloud and on-premises resources in human-readable configuration files. Its workflow moves from writing configuration to generating a plan and applying approved changes in dependency order. Providers connect it with cloud platforms, SaaS services and APIs, including AWS, Azure, Google Cloud Platform, Kubernetes, Helm, GitHub, Splunk and Datadog. Reusable modules and a public registry support configurable infrastructure collections. OpenTofu tracks resources in a state file, builds a dependency graph and can change independent resources in parallel. Built-in client-side state encryption supports key providers such as PBKDF2, AWS KMS, GCP KMS and OpenBao. Providers can be installed from registries, local mirrors or caches, including for air-gapped environments. OpenTofu is presented as a Terraform replacement that preserves existing workflows and configurations. OCI registries can host modules and serve as a secondary provider source, but not yet the primary source. Official installation options cover Linux, macOS, Windows, FreeBSD and OCI container images.