How srajasimman/terraform-aws-github-oidc-iam works
Main Components
a) External Systems:
• GitHub Actions (Source)
• AWS (Target Platform)
b) Core Components:
• OIDC Identity Provider
• IAM Role
• IAM Policies (both custom and existing)
Specific Elements
a) Components:
• Blue: GitHub components
• Orange: AWS components
• Green: Security/Authentication components
b) Connections:
Detailed Flow Representation
[GitHub Actions] --OIDC Token--> [AWS OIDC Provider]
• Trust Policy
• [IAM Role] -----> [Attached Policies]
• [Custom Policy] [Existing AWS] [Additional]
• Policies Policies
Additional Details
• Role assumption process
• Policy attachment points
• A note about the thumbprint validation
Technical Specifications
• Required provider versions (AWS >= 4.0, TLS >= 3.0)
• Terraform version requirement (>= 1.5.0)
• Resource types being created
Implementation Notes
• The modular nature of the policy attachment system
• The flexibility in repository access control
• The security boundary created by the OIDC trust relationship
Optional Elements
• A small section showing example repository patterns
• A mini-view of the policy structure
• Role assumption workflow
• How the OIDC authentication flow works
• Where and how policies are attached
• The security implications of the setup
• The configuration points available through the module variables