
Terraform Registry
Terraform provisions, updates, and destroys infrastructure resources such as physical machines, VMs, network switches, containers, and more. Configurations are code written for Terraform, using the …
Docs overview | hashicorp/aws | Terraform | Terraform Registry
AWS Provider The Amazon Web Services (AWS) provider is Terraform’s most widely-used provider and the industry-standard way to manage AWS infrastructure as code. It is an indispensable part of how …
Docs overview | hashicorp/azurerm - Terraform Registry
Terraform's community resources HashiCorp support for Terraform Enterprise customers Argument Reference The following arguments are supported: features - (Required) A features block as defined …
Browse Providers - Terraform Registry
Providers Providers are a logical abstraction of an upstream API. They are responsible for understanding API interactions and exposing resources.
Guides - Terraform Registry
Install Terraform and read the Terraform getting started guide that follows. This guide will assume basic proficiency with Terraform - it is an introduction to the Google provider. Configuring the Provider …
Docs overview | hashicorp/google - Terraform Registry
Terraform's community resources HashiCorp support for Terraform Enterprise customers Releases Interested in the provider's latest features, or want to make sure you're up to date? Check out the …
hashicorp/azurerm - Terraform Registry
Top downloaded azurerm modules Modules are self-contained packages of Terraform configurations that are managed as a group.
aws - Terraform Registry
Lifecycle management of AWS resources, including EC2, Lambda, EKS, ECS, VPC, S3, RDS, DynamoDB, and more. This provider is maintained internally by the HashiCorp AWS Provider team.
Data Sources | hashicorp/aws - Terraform Registry
Data Sources aws_ ami aws_ ami_ ids aws_ availability_ zone aws_ availability_ zones aws_ ec2_ capacity_ block_ offering aws_ ec2_ host aws_ ec2_ instance_ type aws_ ec2_ instance_ type_ …
azurerm - Terraform Registry
Disclaimer Important to note is that the activation of the Beta should only be done in non-production environments and the activation is non-reversible since the changes in 4.0 will affect the Terraform …