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

**URL:** <https://discuss.circleci.com/t/aws-permissions-are-gone-but-the-values-are-still-available-in-build-environment/29169>\
**Category:** Build Environment\
**Tags:** awscli, aws\
**Created:** [March 21, 2019, 6:16pm UTC](https://discuss.circleci.com/t/aws-permissions-are-gone-but-the-values-are-still-available-in-build-environment/29169 "2019-03-21T18:16:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![aspushkinus](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/aspushkinus/32/10905_2.png) [@aspushkinus](https://discuss.circleci.com/u/aspushkinus)\
**Post date:** [March 21, 2019, 8:40pm UTC](https://discuss.circleci.com/t/aws-permissions-are-gone-but-the-values-are-still-available-in-build-environment/29169/4 "2019-03-21T20:40:18Z")

</div>

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.

---

_[View the full topic](https://discuss.circleci.com/t/aws-permissions-are-gone-but-the-values-are-still-available-in-build-environment/29169)._