What are the steps to configure OpenID Connect between GitHub Actions and AWS IAM so we can deploy our dev tools without hardcoding secret keys?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What are the steps to configure OpenID Connect between GitHub Actions and AWS IAM so we can deploy our dev tools without hardcoding secret keys?
2 real searches · 1 real-search pass
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 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
GitHub Actions OpenID Connect AWS configure IAM role official documentation Google ↗
AWS IAM create OpenID Connect identity provider GitHub Actions official documentation Google ↗
- AWS IAM Console · console.aws.amazon.com
- Create an OpenID Connect (OIDC) identity provider in IAM · docs.aws.amazon.com
- Configuring OpenID Connect in Amazon Web Services · docs.github.com
- Configuring OpenID Connect in Amazon Web Services · docs.github.com
- Create a role for OpenID Connect federation (console) · docs.aws.amazon.com
- Use IAM roles to connect GitHub Actions to actions in AWS · aws.amazon.com
- GitHub - aws-actions/configure-aws-credentials: Configure AWS credential environment variables for use in other GitHub Actions. · github.com
- configure-aws-credentials/README.md at main · aws-actions/configure-aws-credentials · github.com
Queries
2 queries · click a column to sort