darkhelm/notifications-api
1
0
Fork 0
mirror of https://github.com/GSA/notifications-api.git synced 2025-12-20 15:31:15 -05:00
Code Issues Packages Projects Releases Wiki Activity

Explanation of the purpose of bucket credentials

Browse Source
This commit is contained in:
John Skiles Skinner
2024-04-09 11:26:50 -07:00
parent 150cbeb54f
commit e228a02653
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
terraform/README.md
View File

@@ -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 — which it should be if Notify.gov is online — 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.