Management and Governance
CoreService control policies (SCPs)
Explicit multi-account guardrail and effective-permissions boundary.
Key points
- SCPs set maximum permissions for member-account principals at an Organization scope and do not grant access.
Best-known use cases
- D1.1, D1.2, and D3.1: enforce or troubleshoot a named account guardrail while retaining the required IAM allow.
What candidates often confuse it with
- An SCP caps permissions across an Organization scope; IAM policies grant within that boundary and Config evaluates configuration.
Key takeaway
When an SCP is relevant, inspect its attachment scope and explicit denies before adding IAM permissions.
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).