Terraform can store state remotely in S3 and lock that state with DynamoDB. In this Terraform tutorial video, I am going to explain how you can configure remote state on S3 backend and enable state locking with Dynamo DB table.
#terraform
#s3bucket
#remotestate #devops
Connect with me on LinkedIn: / nasiullha-chaudhari-5a...
Timestamps -
1. Intro 0:00 - 0:15
2. Benefits of Remote State 0:16 - 0:43
3. Create S3 bucket for storing State file 01:07 - 06:00
4. Create a DynamoDB table for state locking 06:00 - 08:00
5. Apply changes to create s3 and dynamo DB 08:10 - 09:05
6. Add the backend in terraform block 09:05 - 10:45
7. Run the commands and migrate the state 10:46 - 12:40
8. Test the s3 state file 12:41- 14:30
9. Remote state to local state 14:35
Terraform Remote state documentation: developer.hashicorp.com/terra...
S3 resource: registry.terraform.io/provide...
Dynamodb resource: registry.terraform.io/provide...
Terraform stores its state in the file terraform.tfstate in local filesystem. This works well for personal projects, but working with Terraform in a team, use of a local file makes Terraform usage complicated because each user must make sure they always have the latest state data before running Terraform and make sure that nobody else runs Terraform at the same time.
The best way to do this is by running Terraform in a remote environment with shared access to state. Remote state solves those challenges. Remote state is simply storing that state file remotely, rather than on your local filesystem. With a single state file stored remotely, teams can ensure they always have the most up to date state file.
Terraform Remote State Storage Options
Terraform supports storing state in
Amazon S3
Azure Blob Storage
Google Cloud Storage
Terraform Cloud
HashiCorp Consul
With Remote state configuration all the state is stored in backends like s3 which is considered as a good practice.
Benefits of using Terraform Remote State
Shared Storage: Remote state (Backend) allow each of your team members to access same Terraform state files to manage infrastructure.
Locking: With fully-featured remote backends, Terraform can lock the state file while changes are being made. This ensures all changes are captured, even if concurrent changes are being attempted against the same state.
Without locking, if two team members are running Terraform at the same time, you may run into race conditions as multiple Terraform processes make concurrent updates to the state files, leading to conflicts, data loss, and state file corruption.
Versioning: Some backends support versioning. This maintains versions of your Terraform state files allowing you to download an old version if needed.
Encryption: Many backends support encryption of the state file both in transit and at rest.
Security: A local state file save the content in plain text. It is very common to have secrets or sensitive data in the state, so local state files are insecure
Remote operations: Some backends allow to manage operations remotely (Terraform plan and apply execution). You don’t need to use terraform on your system to apply the changes. You could either trigger it from a Web UI, API call or CLI tool.
Less Manual Errors: Using a local state file as a shared storage, manually sync the changes could cause someone forget to sync the state file. Remote state will always sync the state automatically whenever it change.
Also Checkout my other videos
Terraform playlist: • How to create Amazon E...
How to become DevOps engineer without any experience: • Fresher to Remote DevO...
Important Linux Commands : • Linux commands for Clo...
How I became an AWS Community Builder: • AWS Community Builders...
How to become Cloud Engineer: kzread.infoJShyUFJK0-...
@Cloud Champ is a youtube channel I started to record my learning and now is helping a lot of cloud and devops engineer. If you need any help you can always drop a comment or reach out to me.
Tags:
terraform remote state
terraform backend s3
terraform state backend s3 bucket
terraform remote state s3 example
terraform state in s3 bucket
terraform remote state
terraform remote state s3 example
terraform state in s3 bucket
terraform remote state azure
terraform state locking
terraform state file s3
terraform remote state file
terraform backend s3 example
terraform state backend s3
terraform migrate state to s3
terraform state s3 bucket
terraform state s3 dynamodb
terraform tfstate s3
terraform tutorial
techworld with nana terraform
terraform aws
terraform state management s3
state remote s3
terraform state backend s3
terraform migrate state to s3
terraform state s3 bucket
terraform state s3 dynamodb
terraform tfstate s3