4 ms·
I never knew how easy it was to setup role assuming for AWS/GHA. It’s much easier than managing the access/secret. I wrote a little about it in this blog post:
by joshstrange 2y ago
I never knew how easy it was to setup role assuming for AWS/GHA. It’s much easier than managing the access/secret.
I wrote a little about it in this blog post: https://joshstrange.com/2024/04/26/nightly-postgres-backups-via-github-actions/ https://joshstrange.com/2024/04/26/nightly-postgres-backups-...
- mdaniel 2y agoIf you, or others, are interested I have found that those role-session-name variables make for a great traceability signal when trying to figure out what GHA run is responsible for AWS actions. So instead of role-session-name: GitHubActionSession one can consider role-session-name: gha-${{ github.run_id }} # or your favorite I don't this second recall what the upper limit is on that session name so you may be able to fit quite a bit of stuff in there