Skip to content
Discussion options

You must be logged in to vote

Thanks @mrfelek for the clear write up, and @2SinceJuly for the careful answers.

On (1), backward compatibility is the reason: flipping the default would turn every Lambda or assumed role session with too narrow a role into AccessDenied on upgrade, which is the risk @mrfelek names. So the default stays off for now.

On (3), yes please: one WARN the first time a request signed by an IAM user key or a role session arrives while enforcement is off is the right shape, since it reaches exactly the people whose policies are not checked and stays quiet for the test key workflow.

On (2), I'd revisit the default once the MFA condition keys are in the request context, since today a policy using the a…

Replies: 3 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@mrfelek
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by hectorvent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants