In this project i connect backend as aws " bucket S3" and "DynamoDB"
🌟What is state locking ?
State Locking is terraform inbuild setting used to avoid conflicts and ensure the integrity of Terraform state by preventing concurrent modifications from multiple users or processes.
Note: Not required to set-up "State Locking" when state file save in local, but if we want to save 'terraform state file' in Centralized Storage (Remote Backend) then need to set-up of Terraform State Locking.
🌟Remote State File/ State Locking :--
Remote state file means we can save our "terraform.tfstate" file in Centralized Storage.
Using centralized storage means keeping all Terraform configuration information in one place that everyone on the team can access. It helps everyone work together smoothly and ensures that everyone has the same up-to-date information about the infrastructure. It also adds security features like access control and makes it easier to back up and manage large amounts of data.
⚙️Following steps need to do on AWS console :
⚡Step-1:(Create an S3 Bucket)
Go to aws console search "S3" then click create S3 bucket,in my case name of bucket is "tf-ps", select region same as terraform plugin.
⚡Step-2:(Create a Folder in the Bucket)
After S3 Bucket is created then need to create folder to manage things.
aws console -->> in S3 , Click on S3 bucket("tf-ps") click on create folder and give folder name in my case "webdev" is key name .
Note:-
When we use aws S3 bucket as Backend for terraform state file then terraform state locking not work, For enable 'state-locking' in S3 bucket then we have use "DynamoDB" with "S3". External locking mechanism we used.
⚡Step-3: (DynamoDB table)
on aws console-->> search "dynamoDB" then click on 'Dashboard' , create table in my case name is "table-locking-statefile". Then partition key = LockID .
❄️ Now on Terraform 💻❄️
✧ Step-1:--
#notepad provider.tf
bucket: Specifies the name of the S3 bucket where Terraform state will be stored.
key: Specifies the path within the bucket where the state file will be stored.
region: Specifies the AWS region where the S3 bucket is located.
dynamodb_table: Specifies the name of the DynamoDB table used for state locking.
✧ Step-2:--
#notepad main.tf
This Terraform configuration creates an AWS EC2 instance, referencing the most recent Amazon Machine Image (AMI) meeting specific criteria, and sets up a security group allowing inbound traffic on specified ports.
For this i use Two terminal of same terraform plugin, and form that two terminal(console) i run "terraform apply command"
Note :
For plugin 1st need to run follow command:
# terraform init
And also use to reconfigure precreated
# terraform.exe init -reconfigure
Now terraform apply command run from two terminal at same but only one work:
#terraform apply
In Below screenshot, When 1st terminal(user1) run apply command at same time 2nd terminal(user2) run same apply command, Here only 1st user command work and 2nd user command not work
it goes under 'State Lock'.
✧ After user1 Infrastucture done we again run same apply , the user2 terminal is state locked is now open see in below Screenshot:
✧ State File (terraform.tfstate) is not save locally on Both user/terminal :
Note:
When user2 goes under state locking then ".terraform.lock.hcl" file automatically install on locally .
#ls -a
❄️ On aws Console infrastucture done:
✧ EC2 instance is lanuched by Terraform :
✧ AWS S3 Bucket:(my.state file is created & And here Terraform state save)
✧ AWS DynamoDB (This enable State locking for S3 Bucket):
