Skip to content

Day 5 - Add native S3 state locking tip to Terraform remote backends guide #1931

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sonu7089 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Day 5 - Add native S3 state locking tip to Terraform remote backends guide #1931

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/guides/introduction-to-terraform/09-remote-backends-and-collaboration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,8 @@ terraform {
}
```

> **Tip:** Starting in Terraform 1.10, the S3 backend supports native S3 state locking with `use_lockfile = true` (using S3 conditional writes to create a `.tflock` file alongside your state). On Terraform 1.10+, you can set `use_lockfile = true` instead of `dynamodb_table` to get state locking without provisioning and maintaining a separate DynamoDB table.

Initialize to migrate existing local state:

```bash
Expand Down