AWS and AWSCC Terraform providers: Better together

The AWS and AWSCC Terraform providers are two separate providers that interact with AWS APIs, but they complement each other rather than competing. The AWS provider is built on the AWS SDK and has been around for 10 years, with over three billion downloads, offering a wide range of resources for various AWS services. It's handwritten in Go, ensuring rigorous test coverage but also making it challenging to support all AWS resources, especially day-one support for new services. In contrast, the AWSCC provider is automatically generated from the Cloud Control API and provides launch-day support for new AWS services or features. The AWSCC provider offers a uniform interface, allowing new resources to be automatically generated based on codified rules as soon as new resource schemas are released. Using both providers together equips developers with a large catalog of resources across established and new AWS services. Migrating state between the two providers can be done by refactoring existing code, importing necessary modules, removing old providers, and creating new ones. The article provides examples and best practices for using both providers, as well as resources for further learning.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.