Remote state backends to manage Terraform state

# stage/frontend-app/main.tf
terraform {
  backend "s3" {
    bucket         = "my-terraform-state"
    key            = "stage/frontend-app/terraform.tfstate"
    region         = "us-east-1"
    encrypt        = true
    dynamodb_table = "my-lock-table"
  }
}

terraform {
  backend "s3" {
    bucket = "my-terraform-states"
    key    = "path/to/not/override/other/terraform.tfstate"
    region = "us-west-2"
    dynamodb_table = "my-terraform-states-table"
    profile = "your_profile"
    workspace_key_prefix = "your-prefix"
  }

GitLab 13.0 (2020) can be used as an HTTP backend for Terraform.

terraform {
  backend "http" {}
}

Related

• backend.tf
• GitLab 13.0 (May 2020)

See also

• Terraform configuration files, Terraform state files: .tf, .tfvars, main.tf, outputs.tf, variables.tf, .terraform.d/, terraform init, providers.tf, .terraform/, terraform.tfstate, .terraform.lock.hcl, terraform.tfstate.d, override.tf, versions.tf
• Terraform backends: S3, Terraform S3 backend: dynamodb table, GCS, remote
• Terraform state: terraform [ state | replace-provider | mv ], backend.tf, Remote state backends to manage Terraform state, State locking, terraform force-unlock