Proof of Concept demonstrating how to build resources to store Terraform State & Provider State Locking on AWS via S3 (Object Storage) and DynamoDB (Managed NoSQL DB)
-
Updated
Apr 22, 2019 - HCL
Proof of Concept demonstrating how to build resources to store Terraform State & Provider State Locking on AWS via S3 (Object Storage) and DynamoDB (Managed NoSQL DB)
Establish the base AWS infrastructure for your team with Terraform & Fenna.
multi-layered terraform code layout, directory per service, region, account, remote state in S3 bucket, AWS
Terraform module to create remote state backend for Azure provider
Terraform module to create remote state backend for GCP provider
Yandex Cloud using example by Terraform with Kubernetes and Helm
Terraform module to create remote state backend for AWS provider
In this repository, you'll discover how to effectively manage Terraform state by storing it remotely in AWS S3 and implementing state locking with DynamoDB.
Contains a collection of Terraform files for creating resources in AWS, using variables and various commands, deployment application, terraform configuration files for infrastructure provisioning with explanations and screens
Provision instances on DigitalOcean with Terraform or OpenTofu.
Provision instances on Linode with Terraform or OpenTofu.
Terraform Module to create Terraform state storage backend based on AWS S3 and DynamoDB for state locking.
Terraform module that provision an S3 bucket to store the `terraform.tfstate` file and a DynamoDB table to lock the state file to prevent concurrent modifications and state corruption.
Add a description, image, and links to the remote-state topic page so that developers can more easily learn about it.
To associate your repository with the remote-state topic, visit your repo's landing page and select "manage topics."