1. DynamoDB table with S3 backend is for…
- Storing Docker images
- State locking so two applies do not clash
- User passwords
- ALB logs only
terraform_remote_state
Source: doonops-curriculum/remote-state--remote-state-datasource.md
Doonops lesson
Goal
Read another project's outputs — VPC team → App team.
Simple explanation
Network team publishes vpc_id. App team imports it like phone number from directory.
Technical view
Network team publishes vpc_id. App team imports it like phone number from directory.
Think of it like
Network team publishes vpc_id. App team imports it like phone number from directory.
Steps
- Read simple section
- Read analogy + diagram
- Copy project files
- Do local lab
Deep explanation
Layman words first, then technical detail — read slowly
data.terraform_remote_state — no duplicate VPC.
Example (Doonops)
Modern HCL — names are examples, not from any third-party course
Example HCL
# see project files
Terraform runs on your computer — copy this HCL into a folder, then follow the local lab steps below.
Quick check
- Explain topic to a friend in 2 sentences
- Did local lab steps
Project files for this lab
Full implementation folder — copy all files, then run terraform commands
Lab project files (full folder)
Copy every file below into one folder — same as a real repo module. Then run the local lab steps.
Suggested folder: Suggested path: ~/doonops-terraform/23-remote-state-data/
versions.tfSee file purpose in the code belowterraform {
required_version = ">= 1.9.0"
}
Module check — did you get it?
2–3 quick questions before the next module
Remote state — quick check
Quick check — did this module stick?