The authoritative reference for cross-cloud identity architecture. We cover Google Cloud IAM and Workload Identity Federation in depth, with complete examples for AWS, Azure, and Okta federation.
Senior engineers and architects who need to get identity right across cloud environments. We assume you know the basics; we explain the tradeoffs and tell you what to actually do.
gcp/ GCP-native IAM patterns: service accounts, WIF, org policies, IAM Conditions
aws/ AWS IAM and cross-cloud federation patterns
azure/ Azure Entra ID and cross-cloud federation patterns
okta/ Okta as external IdP for GCP and AWS
cross-cloud/ End-to-end cross-cloud identity flows and comparison references
blog/ Published blog posts
| Topic | Path |
|---|---|
| GCP IAM deep-dive | gcp/iam-deep-dive.md |
| AWS IAM patterns | aws/aws-iam-patterns.md |
| Azure Entra ID patterns | azure/azure-entraid-patterns.md |
| AWS → GCP via WIF | cross-cloud/aws-to-gcp-wif.md |
| Azure → GCP via WIF | cross-cloud/azure-to-gcp-wif.md |
| Okta as external IdP | okta/okta-as-idp.md |
| Multi-cloud comparison matrix | cross-cloud/comparison-matrix.md |
| WIF best practices (blog) | blog/wif-best-practices.md |
All Terraform in this library is organized per-topic and targets Terraform 1.5+. Each directory has a README with required variables and expected outputs. Examples use real resource names — substitute your project IDs, org IDs, and pool names.
cd gcp/terraform
terraform init
terraform plan -var="project_id=my-project" -var="org_id=123456789"See CONTRIBUTING.md. The short version: open an issue first, write accurate content, test all code before submitting, and cite official docs.
Apache 2.0.