Module 15 cheat sheet
One-page revision summary for Multi-Account Governance & FinOps: services, Azure mapping, CLI commands, limits, decision rules, exam traps and cost traps.
Assumes: AWS CLI v2 · AWS SDK for .NET v4 · Terraform / CDK (C#) · Region us-east-1 · facts as stated in the Module 15 lessons; items marked VERIFY there are not repeated as certain here. Verified against official sources on 2026-11-18.
A printable summary of Module 15. Each row links back to the lesson with the detail.
Key services
| Service | What it is for |
|---|---|
| AWS Organizations | Account tree (root, OUs, accounts), consolidated billing, policy attachment |
| Control Tower | Managed landing zone: log archive and audit accounts, Account Factory, controls |
| SCPs / RCPs | Cap what your principals can do (SCP) and what can be done to your resources (RCP); neither grants access |
| Tag policies | Standardise tag keys and values; pair with an SCP and Config to enforce |
| Organisation CloudTrail + log archive account | One trail for all accounts, delivered to a locked S3 bucket |
| Delegated administrators | Run Security Hub, GuardDuty and Config aggregators from a security tooling account, not the management account |
| Config conformance packs | Packaged rules plus queryable configuration history as audit evidence |
| Cost Explorer / Budgets / Anomaly Detection | See, cap-alert and spot unusual spend |
| Cost and Usage Reports (Data Exports) | Line-item billing data in S3, queried with Athena or DuckDB |
| Savings Plans / Compute Optimizer / Trusted Advisor | Commit to usage, rightsize, and feed a cost backlog |
| Well-Architected Tool | Free structured review, risks (HRI/MRI), milestones |
.NET / Azure to AWS
| Microsoft / Azure | AWS |
|---|---|
| Management groups + subscriptions | Organizations OUs + accounts (a heavier wall than a subscription) |
| Azure landing zones | Control Tower landing zone, or an IaC "lite" one |
| Azure Policy (deny) | SCPs and RCPs |
| Azure Policy (audit) | Config rules and conformance packs |
| Defender for Cloud | Security Hub, GuardDuty with delegated admin |
| Activity Log to Log Analytics | Organisation trail to log archive S3 |
| Azure tags and tag policy | Tags, tag policies, activated cost allocation tags |
| Cost Management + exports | Cost Explorer, Budgets, Data Exports (CUR) |
| Reservations / savings plans | Savings Plans, Reserved Instances |
| Azure Advisor | Compute Optimizer, Trusted Advisor |
Most useful CLI commands
| Task | Command |
|---|---|
| Show the tree | aws organizations list-roots · list-organizational-units-for-parent · list-accounts-for-parent |
| Attach / inspect an SCP | aws organizations attach-policy · list-policies-for-target · describe-effective-policy |
| Delegate an admin | aws organizations register-delegated-administrator · list-delegated-administrators |
| Validate a policy before use | aws accessanalyzer validate-policy |
| Trail health and integrity | aws cloudtrail get-trail-status · aws cloudtrail validate-logs |
| Config evidence | aws configservice get-conformance-pack-compliance-summary · select-aggregate-resource-config · get-resource-config-history |
| Activate cost tags | aws ce update-cost-allocation-tags-status |
| Spend and forecast | aws ce get-cost-and-usage · aws ce get-cost-forecast · aws ce get-anomalies |
| Budget | aws budgets create-budget |
| Billing export | aws bcm-data-exports create-export |
| Commitment advice | aws ce get-savings-plans-purchase-recommendation · get-savings-plans-utilization · get-savings-plans-coverage |
| Well-Architected | aws wellarchitected create-workload · create-milestone · list-lens-review-improvements |
Key limits and defaults
| Item | Value | Lesson |
|---|---|---|
| Accounts per organisation | 10 by default, adjustable | Organizations structure |
| OU nesting | 5 levels under the root | Organizations structure |
| SCPs per root, OU or account | 10, including FullAWSAccess | Organizations structure |
| RCPs per target | 5, including the built-in one | Guardrails |
| SCP / RCP size | 10,240 / 5,120 characters | Guardrails |
| Concurrent account creations | 5 | Organizations structure |
| RCP rules | Deny only; Principal must be *; name the service, not * | Guardrails |
| Object Lock | Governance mode can be bypassed with permission; compliance mode cannot, even by root | Centralised logging |
| Cost Anomaly Detection | Runs about three times a day; new monitor about 24 hours; new service about 10 days of history | FinOps foundations |
| Savings Plan terms | 1 or 3 years; all, partial or no upfront; cannot be changed after purchase | Commitments |
| Compute Optimizer lookback | 14 days default; enhanced mode up to 93 days (paid) | Commitments |
| Config advanced queries | A SQL subset: no FROM, JOIN, AS, DISTINCT or HAVING | Compliance evidence |
Decision rules
| If... | Then... |
|---|---|
| Different data scope, duties, quotas or blast radius | Separate account; write down the reason |
| Need an auditable baseline fast and accept the cost | Control Tower; otherwise an IaC "lite" landing zone |
| Block an action everywhere | SCP deny on the OU, tested offline first, staged to a test OU |
| Stop outsiders reaching your S3, KMS, STS, SQS or Secrets Manager resources | RCP |
| Logs must resist administrators | Separate log archive account, SSE-KMS, Object Lock compliance mode |
| Central security view | Delegated administrator account plus auto-enable, never the management account |
| Mandatory tags | Tag policy (values) + SCP (deny create) + Config rule (detect) + IaC default tags |
| Auditor asks for GDPR evidence | Records and decisions; there is no GDPR conformance pack |
| Steady compute usage | Rightsize first, then a Compute Savings Plan sized below your lowest steady usage |
| Allocating shared cost | Showback first from tagged CUR data, then chargeback by agreement |
Common exam traps
- SCPs never grant permissions. They set a ceiling; IAM must still allow.
- SCPs do not affect the management account or service-linked roles.
- RCPs restrict resources; SCPs restrict principals. An SCP deny still applies to the root user of a member account.
- Tag policies standardise tags but do not stop untagged creation. Use an SCP for that.
- Cost allocation tags must be activated in the management account, and activation is not retroactive by default.
- Config shows configuration, not business controls; human evidence is still needed.
- Audit Manager is in maintenance for new accounts; use conformance packs and Security Hub CSPM.
- A Savings Plan is an hourly dollar commitment, not a resource reservation.
- Budgets alert; they do not stop spend unless you configure actions.
- Organizations is a global service homed in us-east-1.
Cost traps
| Trap | Avoid it by |
|---|---|
| Config recorder and conformance pack left on in many Regions | One Region, short session, stop the recorder |
| Control Tower enabling Config and services in every account | Design-only, or the IaC lite landing zone |
| GuardDuty and Security Hub trial forgotten | Disable after the lab; calendar the date |
| Unlimited Athena queries over CUR | Workgroup bytes-scanned cutoff, Parquet, partitions; or DuckDB locally |
| Compliance-mode Object Lock in a lab | Use governance mode for one day |
| Data events and verbose logs everywhere | Scope data events to sensitive buckets; set lifecycle expiry |
| Too-large Savings Plan commitment | Size from your own usage, below the steady floor |
| Untagged spend nobody owns | Weekly tagged-spend percentage; budget per account |
| Accounts created by reflex | Count baseline services, people and quota requests per account |
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.
Well-Architected Tool reviews: Security pillar, Financial Services Industry Lens and tracking improvements
Run a structured Well-Architected review of a Harbourline workload in the AWS Well-Architected Tool, apply the Financial Services Industry Lens, turn high-risk findings into an owned improvement plan, and track progress with milestones and a C# risk report.
Module 16: Generative AI on AWS for Banking
An awareness-level module on using generative AI safely in a bank: Amazon Bedrock models, knowledge bases, guardrails and agents, and AI coding assistants. You learn to call Bedrock from C#, and above all where GenAI fits, where it must not be used without controls, and which risks a bank's model-risk team will ask about.