Module 15: Multi-Account Governance & FinOps
Set up and govern many AWS accounts the way a bank must: organisational units, guardrails, central logging and security tooling, and evidence an auditor can use. You also learn FinOps, so every team can see, explain and reduce what it spends.
Assumes: AWS Organizations · AWS Control Tower · CDK (C#) / Terraform · Region us-east-1. Verified against official sources on 2026-11-18.
Set up and govern many AWS accounts the way a bank must: organisational units, guardrails, central logging and security tooling, and evidence an auditor can use. You also learn FinOps, so every team can see, explain and reduce what it spends.
| Estimated time | About 12 hours (lessons 7 h · labs 3 h · project 2 h) |
| Priority for you | ⭐ High — priority 3 (banking-grade security and governance) |
| Level | Intermediate → advanced |
| Certifications | SCS-C03 · SAP-C03 · SOA-C03 · CLF-C02 |
| Cost profile | 🟢 Organizations, SCPs, tagging, budgets · 🟡 Config, Security Hub, Control Tower (brief, one Region) |
Why this matters in banking
A bank never runs production, development and security tooling in one AWS account. Separate accounts give hard blast-radius boundaries, clear segregation of duties and clean cost reporting. Auditors will ask: who can change production, how do you stop someone disabling CloudTrail, where are logs kept and for how long, and how do you know every account meets your baseline? The finance function will ask why the bill rose 40% last month. This module answers both sets of questions.
Analogy: AWS Organizations is the bank's group structure. Each account is a separate branch with its own vault; service control policies are head-office rules that no branch manager can override; the log archive account is the sealed records room only auditors can open.
From .NET/Azure to AWS
| You know (Microsoft/Azure) | AWS equivalent | What's different |
|---|---|---|
| Management groups + subscriptions | AWS Organizations with OUs + accounts | An account is a stronger isolation boundary than a subscription |
| Azure landing zones | AWS Control Tower landing zone, Account Factory | Control Tower sets up log archive and audit accounts for you |
| Azure Policy (deny) | Service control policies (SCPs) and resource control policies (RCPs) | SCPs cap what principals can do; RCPs cap what can be done to resources |
| Azure Policy (audit) | AWS Config rules and conformance packs | Config records configuration history for evidence |
| Microsoft Defender for Cloud | AWS Security Hub (and Security Hub CSPM), GuardDuty | Delegated administrator accounts centralise findings |
| Azure tags + tag policies | Tags, tag policies, cost allocation tags | Tags must be activated for cost allocation |
| Azure Cost Management | Cost Explorer, Budgets, Cost Anomaly Detection, Cost and Usage Reports | CUR data is queried with Athena or dashboards |
| Azure reservations / savings plans | Savings Plans, Reserved Instances | Commitments can be shared across an organisation |
| Azure Advisor (cost) | AWS Compute Optimizer, Trusted Advisor | Rightsizing recommendations per resource |
| Azure Well-Architected Review | AWS Well-Architected Tool | Lens reviews include the Financial Services Industry Lens |
Learning objectives
By the end of this module you can:
- Design an AWS Organizations structure with OUs for security, infrastructure, workloads and sandbox.
- Explain what AWS Control Tower sets up and when a lighter, IaC-built landing zone is enough.
- Write and test SCPs and RCPs as guardrails, using public examples as a starting point.
- Centralise CloudTrail, Config and security tooling with delegated administrator accounts and aggregators.
- Define a tagging strategy and enforce it with tag policies.
- Collect compliance evidence with AWS Config conformance packs and exports, and explain the limits of automated evidence.
- Run FinOps: budgets per account, Cost Explorer, Cost and Usage Reports, Savings Plans, rightsizing and showback/chargeback.
- Run a Well-Architected Tool review on a workload.
Prerequisites
- Module 0: Orientation — your sandbox organisation, budgets and region-restricting SCP
- Module 5: Security — IAM policy evaluation, CloudTrail, Config, Security Hub
- Module 10: Infrastructure as Code — CDK and Terraform for the landing zone
How the pieces fit
Lessons
- Why a bank uses many AWS accounts — blast radius, segregation of duties, quotas and cost boundaries.
- AWS Organizations structure — OUs for security, infrastructure, workloads and sandbox; the management account's limited role.
- AWS Control Tower and landing zones — what it builds, Account Factory, controls, and when to start lighter with IaC.
- Guardrails with SCPs and RCPs — deny-by-exception patterns, Region restriction, protecting security services, and testing policies safely.
- Lab 15.1: design, test and attach organisation guardrails — the hands-on checkpoint for lessons 1 to 4 (see the labs section below).
- Centralised logging — organisation trail, log archive account, retention and immutability.
- Centralised security tooling — delegated administrators for Security Hub, GuardDuty and Config; Config aggregators.
- Tagging strategy and tag policies — mandatory tags, cost allocation tags and enforcement.
- Compliance evidence — Config conformance packs, advanced queries, configuration history and what still needs human evidence.
- FinOps foundations — Cost Explorer, budgets per account, Cost Anomaly Detection and alerting.
- Cost and Usage Reports — exporting billing data and querying it with Athena or DuckDB for showback and chargeback.
- Commitments and rightsizing — Savings Plans, Reserved Instances, Compute Optimizer and Trusted Advisor.
- Well-Architected Tool reviews — running a review with the Security pillar and Financial Services Industry Lens, and tracking improvements.
When you want a quick revision page, use the Module 15 cheat sheet.
Labs and module project
- Lab 15.1: design, test and attach organisation guardrails (🟢) — describe Harbourline's organisation (OUs, accounts, attached SCPs) as a file, prove with 50 tests that the guardrails block what they should and allow what they must, then optionally attach them to the Sandbox OU with Terraform. The tests run without an AWS account. The code is in
labs/m15-org-guardrails/. - Lab 15.2 (🟢) — coming: tag policy plus cost allocation tags, and a budget per account with email alerts. The steps are in Tagging strategy and tag policies and FinOps foundations in the meantime.
- Lab 15.3 (🟡) — coming: AWS Config with the PCI DSS v4.0 conformance pack in one Region for a short session, an evidence export with an advanced query, then disable it. The walkthrough is in Compliance evidence.
- Lab 15.4 (🟢) — coming: query a sample Cost and Usage Report with Athena (or DuckDB locally) to build a showback report per tag. The method is in Cost and Usage Reports.
Module project — landing zone (lite) design and build. Define the OU structure, SCPs, central CloudTrail, Config aggregator, Security Hub delegated admin, IAM Identity Center permission sets and budgets as code. Lab 15.1 gives you the first part (OUs and SCPs with tests); the logging and security tooling lessons add the rest. This is the core of Capstone 7 — Secure Multi-Account Landing Zone (lite).
Cost profile
| Part | Label | Free alternative |
|---|---|---|
| Organizations, OUs, SCPs, RCPs, tag policies | 🟢 free | No charge for Organizations itself |
| AWS Budgets, Cost Explorer basics | 🟢 free | A small number of budgets is free ⚠ VERIFY current allowance |
| Organisation CloudTrail (management events, first copy) | 🟢 free | S3 storage for the logs costs a few cents |
| AWS Config rules and conformance packs | 🟡 credits | One Region, short session, then stop the recorder |
| Security Hub / GuardDuty | 🟡 credits | Use the free trial period in one Region, then disable (trial terms ⚠ VERIFY) |
| AWS Control Tower | 🔴 paid | Design-only, or the IaC "lite" landing zone, because it enables Config and other services across accounts |
| Cost and Usage Reports with Athena | 🟡 credits | Query a small sample locally with DuckDB |
Certification alignment
| Exam | Domains (weight) | What this module covers |
|---|---|---|
| SCS-C03 | Governance (14%) · Detection (16%) | Guardrails, central logging, evidence |
| SAP-C03 | Security & Governance · Cost (weights ⚠ VERIFY) | Multi-account strategy and cost governance |
| SOA-C03 | Security (16%) | Config, Organizations, cost monitoring |
| CLF-C02 | Billing (12%) · Security (30%) | Billing tools, pricing models, Organizations |
The domain labels are short forms; see each exam page for the official wording.
Service availability notes
Governance service changes — verified 2026-11-17
AWS Audit Manager is in maintenance: since 2026-04-30 it can no longer be set up in new accounts. AWS points to AWS Config conformance packs, AWS Control Tower controls and Security Hub CSPM standards, plus partner tools for full evidence management. There is a PCI DSS v4.0 conformance pack, but no GDPR or SOC 2 conformance pack — UK GDPR evidence remains a legal and compliance exercise, not a dashboard.
AWS Security Hub: the original service is now called AWS Security Hub CSPM; a new unified AWS Security Hub became generally available in December 2025 and correlates findings from GuardDuty, Inspector, Security Hub CSPM and Macie.
AWS Usage Report is in maintenance; use Cost and Usage Reports delivered through billing data exports (current name and version ⚠ VERIFY).
Key AWS services
AWS Organizations · AWS Control Tower · Service control policies · Resource control policies · Tag policies · IAM Identity Center · AWS CloudTrail · AWS Config (rules, conformance packs, aggregators) · AWS Security Hub / Security Hub CSPM · Amazon GuardDuty · AWS Cost Explorer · AWS Budgets · AWS Cost Anomaly Detection · AWS Cost and Usage Reports · Savings Plans · AWS Compute Optimizer · AWS Trusted Advisor · AWS Well-Architected Tool · Amazon Athena
Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.
Module 14 cheat sheet
One-page revision summary for Advanced Banking Architecture: services, Azure mapping, CLI commands, limits, decision rules, exam traps and cost traps.
Why a bank uses many AWS accounts
Decide when to split workloads into separate AWS accounts, justify each split with blast radius, segregation of duties, quotas, data scope and cost, and write the decision down so an auditor can follow it.