How should I structure AWS IAM policies for a CI/CD pipeline running on GitHub Actions so we do not expose our production environment keys?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How should I structure AWS IAM policies for a CI/CD pipeline running on GitHub Actions so we do not expose our production environment keys?
1 real search · 1 real-search pass
AWS IAM GitHub Actions OIDC configure role trust policy GitHub official documentation least privilegeGoogle ↗
OBSERVED
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 1 queries…
Searches and sources
ChatGPT1 real searches · gpt-6
AWS IAM GitHub Actions OIDC configure role trust policy GitHub official documentation least privilege Google ↗
- GitHub - aws-actions/configure-aws-credentials: Configure AWS credential environment variables for use in other GitHub Actions. · github.com
- Configuring OpenID Connect in Amazon Web Services · docs.github.com
- Create a role for OpenID Connect federation (console) · docs.aws.amazon.com
- configure-aws-credentials/README.md at main · aws-actions/configure-aws-credentials · github.com
- Use IAM roles to connect GitHub Actions to actions in AWS · aws.amazon.com