configure-aws-credentials icon indicating copy to clipboard operation
configure-aws-credentials copied to clipboard

Region is getting masked

Open vesubramanian opened this issue 3 years ago • 6 comments

On using this action, the region is also getting masked.

vesubramanian avatar Jan 25 '22 11:01 vesubramanian

Got my solution if we don't want your aws region to get masked please don't use it as a secret like {{secrets.AWS_REGION}} simply hard code it in our workflow commands.

yaldram avatar Sep 05 '22 17:09 yaldram

  • name: Configure AWS Credentials uses: aws-actions/configure-aws-credentials@v1 with: aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} aws-region: ap-south-1

yaldram avatar Sep 05 '22 17:09 yaldram

I am not using it as a secret. But instead of hard coding it, I use a variable. But still it is masked.

vesubramanian avatar Sep 05 '22 17:09 vesubramanian

This action doesn't set the region as a secret in code like it does with the keys. Can you please share reproduction steps i.e. your workflow file @vesubramanian?

peterwoodworth avatar Oct 11 '22 21:10 peterwoodworth

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

github-actions[bot] avatar Oct 17 '22 00:10 github-actions[bot]

PFB. I am not at all using region as a secret, but reading from the matrix. But still it is masked in the output. You can try this. When I reached out to the support, they were also able to reproduce this and they said, they have communicated this to the engineering team, who were also able to reproduce this. But they haven't given an ETA for the fix.

- name: Configure AWS Credentials for Target Account uses: aws-actions/configure-aws-credentials@v1 with: aws-access-key-id: ${{ secrets[env.ACCESS_KEY_ID_VAR] }} aws-secret-access-key: ${{ secrets[env.ACCESS_KEY_VAR] }} aws-region: ${{ matrix.region }} mask-aws-account-id: 'false'

vesubramanian avatar Oct 17 '22 05:10 vesubramanian

I wasn't able to reproduce this @vesubramanian,

When I reached out to the support, they were also able to reproduce this and they said, they have communicated this to the engineering team, who were also able to reproduce this

This is interesting to me, I'm not sure which team they reached out to. Do you have any sort of reference to this support issue so I can try to look it up?

peterwoodworth avatar Nov 01 '22 22:11 peterwoodworth

Please feel free to ping me if this issue persists and you have more info on how I can reproduce it. Thanks

peterwoodworth avatar Feb 21 '23 23:02 peterwoodworth

⚠️Comment Visibility Warning⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

github-actions[bot] avatar Feb 21 '23 23:02 github-actions[bot]