AWS Permissions are gone, but the values are still available in build environment

Build Environment
,
4

Thanks for looking into this.

The following workaround did work for us:

- run: AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID_TEMP AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY_TEMP aws s3 sync ./assets/ s3://fake-bucket-name/assets
- run: AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID_TEMP AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY_TEMP aws s3 sync ./packs/ s3://fake-bucket-name/packs

Basically, I added AWS_ACCESS_KEY_ID_TEMP and AWS_SECRET_ACCESS_KEY_TEMP as environment variables and then explicitly set them before the AWS CLI command.

1 Like