Difference between revisions of "Terraform backends"
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
} | } | ||
} | } | ||
| + | |||
| + | Successfully configured the backend "s3"! Terraform will automatically | ||
| + | use this backend unless the backend configuration changes. | ||
| + | |||
== Related terms == | == Related terms == | ||
Revision as of 08:11, 20 September 2021
Related: Bucket versioning
terraform {
backend "s3" {
bucket = "your-terraform-states"
key = "terraform.tfstate"
region = "us-west-2"
dynamodb_table = "your-terraform-states"
profile = "your-profile"
workspace_key_prefix = "your-workspace"
}
}
Successfully configured the backend "s3"! Terraform will automatically use this backend unless the backend configuration changes.
Related terms
See also
- Terraform, OpenTofu, Terrakube.org, Installation, Terraform AWS, Terraform GCP, Terraform commands, Terraform Cloud, Terraform Enterprise (TFE), HCL, HIL, meta-arguments, providers, modules, resource, provisioners, data sources, backends: remote backends, examples, configuration files, state files, variables, types, Terraform Registry, conditionals:
depends_on, functions, Blocks, dynamic blocks, errors, Terragrunt, Terraformer, Terratest, Terraform certifications, Terraform map type, Terraform Associate, Terraform: list type,TF_VAR_, TF_LOG, Terraform provider versioning, Terraform Style Conventions, Required version, Terraform plugin, Terraform Named Values, tags, Changelog,tfsec, tflint, Operators, Expressions:for, splat, Debugging, Namespaces, Terraform Landing Zones, CDKTF, Atmos
Advertising:
