Skip to content

Commit

Permalink
Add "unset-current-credentials: true" to CI/CD
Browse files Browse the repository at this point in the history
Yesterday, I started creating an AWS SAM CI/CD pipeline using GitHub
Actions, which isn't yet deployed.

Today, the mbland/elistman pipeline started failing while trying to
configure AWS credentials after pushing commit
4841ade:

- https://github.com/mbland/elistman/actions/runs/6149590436/job/16686549484
  Error: The security token included in the request is invalid.

I tried to update the trust policy for the relevant IAM user, which I'd
seen had been updated to trust requests from mbland/ses-forwarder. I
manually edited it back to mbland/elistman. Rerunning the job still
failed.

I then updated the pipeline to aws-actions/configure-aws-credentials@v3
in commit 60463bc, but it still failed:

- https://github.com/mbland/elistman/actions/runs/6149930473/job/16686849270

Searching for related issues turned up the possibility of trying
"unset-current-credentials: true":

- https://github.com/aws-actions/configure-aws-credentials#unset-current-credentials
- aws-actions/configure-aws-credentials#383

Trying it to see how it goes.
  • Loading branch information
mbland committed Sep 11, 2023
1 parent 60463bc commit aed7091
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions .github/workflows/pipeline.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,7 @@ jobs:
role-session-name: testing-packaging
role-duration-seconds: 3600
role-skip-session-tagging: true
unset-current-credentials: true

- name: Validate SAM template
run: |
Expand Down

0 comments on commit aed7091

Please sign in to comment.