The Terraform Registry makes it easy to use any provider or module. To use a provider or module from this registry, just add it to your configuration; when you run `terraform init`, Terraform will …

Hard-coded credentials are not recommended in any Terraform configuration and risks secret leakage should this file ever be committed to a public version control system.

To learn the basics of Terraform using this provider, follow the hands-on get started tutorials. Interested in the provider's latest features, or want to make sure you're up to date?

Top downloaded aws modules Modules are self-contained packages of Terraform configurations that are managed as a group.

To ensure security, it's best practice to create a dedicated user and role for Terraform instead of using cluster-wide Administrator rights. The particular privileges required may change but here …

To use the provider you can download the binaries from Releases to your local file system and configure Terraform to use your local mirror. See the Explicit Installation Method Configuration …

The root issue lies with the order in which Terraform itself evaluates the provider blocks vs. actual resources. Please refer to this section of Terraform docs for further explanation.

The provider needs to be configured with the proper credentials before it can be used. It requires terraform 0.12 or later. Try the hands-on tutorial on the Datadog provider on the HashiCorp …

Custom endpoints can be configured for the Terraform AWS Provider by configuring them directly on the provider, using environment variables, or by using an AWS shared configuration file.

If omitted, Terraform will assign a random, unique name. This name must be unique per region per account, can have a maximum of 32 characters, must contain only alphanumeric …