INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Separate the principal side of an SCP from the resource side of an RCP in one request.

Prerequisite

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.

A request reaches a resource in a member account
A request reaches a resource in a member account1: External principal — Identify the request — Action. 2: Action — Check the owner — Member resource. 3: Member resource — Apply the resource ceiling — Resource ceiling123External principalActionMember resourceResource ceilingA request reaches a resource in a member account1: External principal — Identify the request — Action. 2: Action — Check the owner — Member resource. 3: Member resource — Apply the resource ceiling — Resource ceiling123ExternalprincipalActionMember resourceResourceceiling
  1. External principal → ActionIdentify the request
  2. Action → Member resourceCheck the owner
  3. 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

An RCP in the fictional organization denies the selected read from outside the organization.
RequestGrant and RCPDecision
Internal readGrant exists; no RCP denyCheck remaining requirements
External readBucket grant; RCP deniesDenied
Internal writeNo grant; no RCP denyPermission has not been granted
Management account resourceDifferent bucketDo 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.

What do you identify first for an RCP?
Read the answer and reason

Answer: Resource owner and service support · Start with whether the resource is covered.

A bucket grants an external caller access but its RCP denies the request. What happens?
Read the answer and reason

Answer: The request is denied · The resource-side ceiling applies.

Does the absence of an RCP deny grant access?
Read the answer and reason

Answer: Check the effective grant · An access grant is required separately.

Check, then explain in your own words

  1. Check the resource type and owner.
  2. Evaluate grants and ceilings separately.
  3. 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.