TerraformProviderAws
terraform-provider-aws is HashiCorp's official Terraform provider for Amazon Web Services, the standard way to define AWS infrastructure as Terraform configuration. It has been maintained since 2017, ships weekly releases, and is licensed under the Mozilla Public License 2.0.
The provider covers the great majority of AWS's service surface through individually hand-written resources and data sources, in contrast to HashiCorp's newer companion provider, awscc, which instead wraps the AWS Cloud Control API to gain near-instant coverage of new resource types at the cost of a less polished, less idiomatic HCL surface. The two are complementary: awscc fills gaps for services the classic provider hasn't caught up to yet.
Community-reported friction concentrates in a handful of stateful, order-sensitive resources rather than missing coverage: provider initialization occasionally freezes during credential validation, assume_role does not always request an MFA token code when one is required, skip_final_snapshot is sometimes ignored on RDS cluster destroy, and services like ECS and ALB target groups have shown non-idempotent create/destroy ordering. These are the kind of bugs that surface on complex, frequently-changed infrastructure rather than on a first terraform apply.
The provider has been used directly against real AWS infrastructure in awscode (2021), a Terraform starter project that provisions VPCs, internet gateways, and subnets across multiple regions with an S3-backed remote state -- the presence of a populated terraform.tfstate confirms an actual apply against a live AWS account, not just a dry-run plan.
It has also been used against a local AWS emulator rather than real AWS: examprep-terraform (2024) documents a runbook for pointing the standard aws provider at LocalStack by skipping credential and account-ID validation and overriding the IAM endpoint to http://localhost:4566.
The provider works unmodified against local AWS emulators through the same endpoint-override mechanism shown in the LocalStack runbook above. radar/tools/Floci and radar/tools/MiniStack are both wire-compatible with that same convention (port 4566, test/test credentials), so switching between real AWS, LocalStack, Floci, or MiniStack is a matter of endpoint configuration rather than a provider or code change.
terraform-provider-aws is placed in Trial: the first-person use above clears the bar this wiki sets for Trial (production use against a real account, not just third-party reputation). The provider's age, weekly release cadence, and broad adoption (11k+ stars, 10k+ forks) support continued reliance on it as the default way to provision AWS infrastructure as code. Known friction points (assume_role MFA, RDS snapshot skipping, ECS/ALB ordering) are narrow enough to work around rather than reasons to avoid the tool.
