Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 21 Packages Projects Releases Wiki Activity

Update enable cloudfront directions (#31152)

Browse Source 
Just a couple small changes to help with the instructions
This commit is contained in:
Janis Watts
2025-07-22 16:31:12 -05:00
committed by GitHub
parent fea2b40cd8
commit 7085ad2a74
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
infrastructure/loadtesting/terraform/readme.md
+4 -3
View File
@@ -77,9 +77,9 @@ This has an impact on real devices because they will not be notified of any comm
### Enabling Cloudfront
> Do not commit your `BRANCH_NAME` if any files exist in `resources/TERRAFORM_WORKSPACE/` without a .encrypted extension.
> This step assumes that you've already successfully executed terraform apply and have a `kms_key_id` output.
> This step assumes that you've already successfully executed terraform apply and have a `kms_key_id` from the output of the terraform apply command.
1. Under the loadtesting directory, create directory `resources/TERRAFORM_WORKSPACE/`. Your `TERRAFORM_WORKSPACE` value can be retrieved with `terraform workspace show`.
1. Under the terraform directory, create directory `resources/TERRAFORM_WORKSPACE/`. Your `TERRAFORM_WORKSPACE` value can be retrieved with `terraform workspace show`.
2. Change directory to `resources/TERRAFORM_WORKSPACE/`
@@ -120,7 +120,8 @@ fi
aws kms encrypt --key-id "${1:?}" --plaintext fileb://<(cat "${2:?}") --output text --query CiphertextBlob > "${3:?}"
```
5. Encrypt the objects using `encrypt.sh`
5. Make the script executable by running `chmod +x ../../encrypt.sh`
6. Encrypt the objects using `encrypt.sh`
```
for i in *; do ../../encrypt.sh <KMS_KEY_ID> $i $i.encrypted; done