AWS introduced a powerful governance tool that many teams may have overlooked:
Resource Control Policies (RCPs).
In large AWS environments, giving admins enough permissions while preventing risky actions has always been difficult.
SCPs control:
→ What identities can do
RCPs control:
→ What resources will allow
Example:
Even if someone has AdministratorAccess, an organization-level RCP can still prevent:
-Public S3 exposure
-Removing security protections
-Breaking compliance rules
For companies running dozens or hundreds of AWS accounts, this adds a powerful safety layer.
A simple way to think about it:
IAM = Who can do what
SCP = What accounts can do
RCP = What resources will accept
AWS governance is moving from “trust users not to make mistakes” to “design guardrails that prevent mistakes.”
Have you started using RCPs in your AWS Organization?
#
AWS# #
DianMirCloud# #
cloudserver#