mirror of
https://github.com/cisagov/manage.get.gov.git
synced 2025-07-25 12:08:40 +02:00
Add instructions for .env
This commit is contained in:
parent
1859d56ddf
commit
ff446aa56a
1 changed files with 18 additions and 1 deletions
|
@ -334,4 +334,21 @@ To associate a S3 instance to your sandbox, follow these steps:
|
|||
7. Under the dropdown on `Select Plan`, select `basic-sandbox`
|
||||
8. Under `Service Instance` enter `getgov-s3` for the name
|
||||
|
||||
See this [resource](https://cloud.gov/docs/services/s3/) for information on associating an S3 instance with your sandbox through the CLI.
|
||||
See this [resource](https://cloud.gov/docs/services/s3/) for information on associating an S3 instance with your sandbox through the CLI.
|
||||
|
||||
### Testing your S3 instance locally
|
||||
To test the S3 bucket associated with your sandbox, you will need to add four additional variables to your `.env` file. These are as follows:
|
||||
|
||||
```
|
||||
AWS_S3_ACCESS_KEY_ID = "{string value of `access_key_id` in getgov-s3}"
|
||||
AWS_S3_SECRET_ACCESS_KEY = "{string value of `secret_access_key` in getgov-s3}"
|
||||
AWS_S3_REGION = "{string value of `region` in getgov-s3}"
|
||||
AWS_S3_BUCKET_NAME = "{string value of `bucket` in getgov-s3}"
|
||||
```
|
||||
|
||||
You can view these variables by running the following command:
|
||||
```
|
||||
cf env getgov-{app name}
|
||||
```
|
||||
|
||||
Then, copy the variables under the section labled `s3`.
|
Loading…
Add table
Add a link
Reference in a new issue