From e228a0265373e130a9dca0700514ef6fb38936e9 Mon Sep 17 00:00:00 2001
From: John Skiles Skinner <john.skinner@gsa.gov>
Date: Tue, 9 Apr 2024 11:26:50 -0700
Subject: [PATCH] Explanation of the purpose of bucket credentials

---
 terraform/README.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/terraform/README.md b/terraform/README.md
index 1890e409d..096c360aa 100644
--- a/terraform/README.md
+++ b/terraform/README.md
@@ -4,7 +4,9 @@ This directory holds the Terraform modules for maintaining Notify.gov's infrastr
 
 ## Retrieving existing bucket credentials
 
-:green_book: Assuming [initial setup](#initial-setup) is complete, new developers start here!
+:green_book: new developers start here!
+
+Assuming [initial setup](#initial-setup) is complete &mdash; which it should be if Notify.gov is online &mdash; Terraform state is stored in a remote backend. If you are going to be developing Terraform, you'll need to hook up to this backend:
 
 1. Enter the bootstrap module with `cd bootstrap`
 1. Run `./import.sh` to pull existing terraform state into the local state
@@ -21,6 +23,8 @@ This directory holds the Terraform modules for maintaining Notify.gov's infrastr
     aws_secret_access_key = <secret_access_key from bucket_credentials>
     ```
 
+These credentials will allow Terraform to access the AWS/Cloud.gov bucket in which developers share Terraform state files.
+
 ## Initial setup
 
 These instructions were used for deploying the project for the first time, years ago. We should not have to perform these steps again. They are provided here for reference.