Management and Governance
CoreAWS Organizations
Explicit multi-account security strategy.
Key points
- Organizations establishes the multi-account hierarchy in which delegated administration and SCP guardrails operate.
Best-known use cases
- D1.1, D1.2, and D3.1: apply or troubleshoot a named multi-account control at the correct root, OU, or account scope.
What candidates often confuse it with
- Organizations groups accounts; SCPs cap member-account permissions and IAM Identity Center assigns workforce access.
Key takeaway
Identify the hierarchy scope and the specific policy or delegated service before changing an Organization.
Related services
- AWS Auto Scaling
- AWS CDK
- AWS CloudFormation
Relevant exam tasks
- D1.1 — Task 1.1: Implement metrics, alarms, and filters by using AWS monitoring and logging services.
- 1.1.1 — Use AWS services (for example, Amazon CloudWatch, AWS CloudTrail, Amazon Managed Service for Prometheus) to configure monitoring and logging for workloads (for example, serverless, compute, AI).
- D1.2 — Task 1.2: Identify and remediate issues by using monitoring and availability metrics.
- 1.2.1 — Analyze performance metrics and automate remediation strategies by using AWS services and functionality (for example, CloudWatch, Lambda, AWS Systems Manager, CloudTrail, Kiro, AWS DevOps Agent).
- D3.1 — Task 3.1: Provision and maintain cloud resources.
- 3.1.1 — Create and manage AMIs and container images (for example, EC2 Image Builder).