Add AWS IAM configuration guide for GitHub Actions#5
Open
pulumi[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Added documentation for configuring AWS IAM trust policy to enable GitHub Actions to use the ESC environment
aws-login/pulumi-dev-sandbox-env.Current Issue
The GitHub Actions workflow is properly configured and
PULUMI_ACCESS_TOKENis set, but the AWS IAM role used by the ESC environment doesn't trust GitHub's OIDC provider.Error:
Solution
The new
AWS_IAM_SETUP.mdfile provides step-by-step instructions to:IAM Role
Role:
arn:aws:iam::616138583583:role/pulumi-esc-oidc-test-org-ijh-AdministratorAccess-roleNeeds trust policy updated to include GitHub Actions OIDC provider.
Once Configured
After the AWS IAM trust policy is updated, the GitHub Actions workflow will automatically work for:
All infrastructure is already deployed and operational.