2. Odds reduced by me posting this
2. Odds reduced by me posting this
Not only that, we can set trust boundaries for IAM roles (e.g. only directly exempted accounts can AssumeRole into our org's identities). More here:
github.com/aws-samples/...
/fin
Not only that, we can set trust boundaries for IAM roles (e.g. only directly exempted accounts can AssumeRole into our org's identities). More here:
github.com/aws-samples/...
/fin
It follows, that SCPs can only be used to limit identities coming from within the org itself (and our cool kittens cannot be defended by them).
However- fear not - RCPs are here to save the day! 🦸♀️
It follows, that SCPs can only be used to limit identities coming from within the org itself (and our cool kittens cannot be defended by them).
However- fear not - RCPs are here to save the day! 🦸♀️
Simplifying slightly, a request is authorized by the principal's account, and by the resource, so...
Simplifying slightly, a request is authorized by the principal's account, and by the resource, so...
A talk I gave about SCP strategy at fwd:cloudsec: www.youtube.com/watch?v=oomo...
A talk I gave about SCP strategy at fwd:cloudsec: www.youtube.com/watch?v=oomo...
Group 2, Let's learn about RCPs! Group 3, we're going to get to that soon.
Before we understand RCPs, we have to understand SCPs (Service Control Policies) first. SCPs are the guardrails of IAM policies, they set up ground rule for what everyone can and can't do.
Group 2, Let's learn about RCPs! Group 3, we're going to get to that soon.
Before we understand RCPs, we have to understand SCPs (Service Control Policies) first. SCPs are the guardrails of IAM policies, they set up ground rule for what everyone can and can't do.