State, Collaboration and Security

4 min

In your code you write a logical address such as:

hcl
resource "aws_s3_bucket" "documents" {
  bucket = "entreprise-documents-exemple"
}

AWS assigns a real identity to the resource. Terraform must remember that aws_s3_bucket.documents corresponds to this precise bucket. The state keeps this association as well as the necessary metadata. HashiCorp describes the state as the mechanism that links the resource instances in the code to the real objects. Official reference — Purpose of the state

Without this correspondence, Terraform would not reliably know which object to modify or destroy.

Preview — the rest of the lesson is for enrolled readers.

Already enrolled with a code?

Your access is tied to your account, not to this link. Sign in with the same email you used in class: your course is waiting, no need to enter the code again.

Sign inNo account yet? Create one
This lesson is part of the “State, Security, Network and Identities” module

The first modules of the course are open to everyone. For the rest you have three options: buy this course once and for all, subscribe, or enter the code handed out in class.

Are you a student on this course?

The code is tied to your account: sign in or create an account and it will be applied automatically when you come back.

No account yet? Create one