Topic lessonTopic: Multi-account guardrails and deployment checks
AWS RCP permissions ceilings for resources in member accounts
Start by identifying the account that owns the destination resource. Separate the principal side of an SCP from the resource side of an RCP in one request.
Separate the principal side of an SCP from the resource side of an RCP in one request.
This example uses a fictional supported S3 general-purpose bucket.
Put the caller and the resource side by side
RCPs define maximum permissions for supported resources in member accounts. An applicable rule can restrict access by external principals.
- External principal → ActionIdentify the request
- Action → Member resourceCheck the owner
- Member resource → Resource ceilingApply the resource ceiling
- External principal
- Fictional partner
- Action
- Read an S3 object
- Member resource
- Bucket inside the organization
- Resource ceiling
- Applicable RCP denies the request
Compare several requests to one bucket
| Request | Grant and RCP | Decision |
|---|---|---|
| Internal read | Grant exists; no RCP deny | Check remaining requirements |
| External read | Bucket grant; RCP denies | Denied |
| Internal write | No grant; no RCP deny | Permission has not been granted |
| Management account resource | Different bucket | Do not use this RCP to determine access |
Read SCP and RCP scopes independently. An absent RCP denial does not grant access.
Test representative internal and external requests
Verify service support. Match the operation, resource type, owning account and any exceptions against official documentation.
Keep necessary integrations in scope. Exercise both permitted and prohibited partner paths in synthetic cases before applying a change.
Record the reason. Identify the policy that grants access and the ceiling that denies it independently.
Check the worked example
Choose an option to see the result and explanation.
Check, then explain in your own words
- Check the resource type and owner.
- Evaluate grants and ceilings separately.
- Validate internal and external requests using synthetic evidence.
Check your understanding: Which side do you inspect first for SCPs and RCPs?
Check the principal for SCP scope and the resource for RCP scope.
The two controls apply to different sides of the request.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- Resource control policiesChecked:
Scope and conditionsSupported member-account resources and applicability to external principals.
Used in this lessonPut the caller and the resource side by side Compare several requests to one bucket Test representative internal and external requests