Open benbridts opened 6 months ago
We can't publish anything that needs IAM permissions other than PassRole.
That's an annoying restriction.
The workaround for that is to:
sts:assumeRole
is not an iam
actionIt's annoying to do that, and the security win of blocking iam
is roughly 0; needing the consumer to not put iam:*
in the role that's attached during the activation, or needing them to not add it to the role that is passed as a property, leaves the same responsibility for the user.
That being said,
It would be nice if that was gated behind CAPABILITY_IAM
both during activation and stack deployment.
Edit: Is there any interest in accepting the hacky-workaround as a code change, or do we want to give a good example here?
I think we should leave the example as it is for now. I'll bring up the possibility of removing the restriction again internally.
What type of extension are you looking for?
Resource
Describe the extension you'd like to request
AwsCommunity::IAM::PasswordPolicy exists in source code form, it would be great if I could activate it in my account without having to build/publish it myself.
Describe the solution you'd like
AwsCommunity::IAM::PasswordPolicy being available as a Third Party Public Extension
Additional context
No response
Is this something that you'd be interested in working on?
Would this feature include a breaking change?