Resource control policies (RCPs): what it can block and where it stops
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Resource control policies (RCPs) is a AWS mechanism. AWS documents RCPs as an AWS Organizations policy type that sets the maximum available permissions for resources in member accounts. It applies to resources of supported services in member accounts, for any principal calling them; not resources in the management account and not service-linked roles.
All mechanisms ยท AWS guardrails
AWS documents RCPs as an AWS Organizations policy type that sets the maximum available permissions for resources in member accounts. They apply to requests against those resources regardless of whether the caller belongs to the organization, and they grant no permissions.
AWS documents an RCP as an AWS Organizations policy type that sets the maximum available permissions for resources in member accounts. RCPs apply to requests against those resources whether or not the caller belongs to the organization, and grant no permissions. They do not affect resources in the management account or restrict service-linked roles.
Limits: a maximum document size of 5,120 characters, and at most 5 RCPs per root, OU or account, the default RCPFullAWSAccess policy included. The IAM policy simulator does not support RCPs, and AWS suggests reviewing CloudTrail logs for Access Denied errors before attaching one. 6 library entries use RCPs, covering controls such as requiring HTTPS and TLS 1.2 for resources.
Documented limits
- RCPs do not affect resources in the management account. (source)
- RCPs do not restrict service-linked roles. (source)
- Maximum RCP document size is 5120 characters. (source)
- At most 5 RCPs can be attached to a root, OU or account, and the default RCPFullAWSAccess policy counts toward that quota. (source)
Testing before enforcement
AWS documents that the IAM policy simulator does not support RCPs; AWS suggests reviewing CloudTrail logs for Access Denied errors before attaching an RCP. (source)
The 6 library entries written in it
- Require HTTPS for access to resourcesAWS, Resource control policies (RCPs), encryption and keys
- Require TLS 1.2 or later for S3AWS, Resource control policies (RCPs), encryption and keys
- Deny changes to S3 Block Public Access at bucket levelAWS, Resource control policies (RCPs), public exposure
- Deny unauthenticated access to Cognito identity poolsAWS, Resource control policies (RCPs), public exposure
- Deny S3 customer-provided encryption keys (SSE-C)AWS, Resource control policies (RCPs), encryption and keys
- Restrict access to resources in a suspended OUAWS, Resource control policies (RCPs), organization integrity
Where Act is behind
Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.
Related pages
Sources
- Resource control policies (RCPs), read 10 Nov 2026
- Limit, read 10 Nov 2026
- Testing, read 10 Nov 2026
Last reviewed 16 Nov 2026.