01
Compare account, subscription, project and organisation models
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
GitHub Actions Academy · Enterprise Knowledge Graph
Multi-Cloud Governance Knowledge Graph
Connect Azure, AWS and GCP through common principles for identity, networking, policy, security, operations, cost and delivery.
Objective: Create consistent governance outcomes without forcing incompatible cloud services into a single technical pattern.
Practical guidance
Foundations and prerequisites
02
Understand each provider identity, network and policy hierarchy
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Define shared business, regulatory and operational requirements
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
Practical guidance
Technology relationships and dependencies
01
Federated identity and central security provide cross-cloud control points
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
02
Cloud-native networking and resource policies remain provider-specific
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Common telemetry, tagging and ownership metadata support oversight
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
Practical guidance
Architecture, delivery and operations
01
Define minimum guardrails and provider-specific implementation standards
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
02
Use reusable pipeline and infrastructure patterns with clear boundaries
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Create cross-cloud FinOps, incident and exception processes
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
Practical guidance
Validation and learning evidence
01
Validate equivalent outcomes rather than identical configurations
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
02
Test access, logging, recovery and cost-allocation coverage
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Maintain a decision record for portability and provider dependency
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.