mach-composer-cli
mach-composer-cli copied to clipboard
Should we execute individual component deployments with individual IAM AssumeRole (in case of AWS)?
To limit permission scope for rolling out individual components, that might be built by different teams, we could consider to execute these with individual set of permissions.
Discussed with @mvantellingen
@pimvernooij do you think this is still relevant? I imagine this is more related to the whole concept of stacks, where one team works on a single stack and should be able to use their team permissions on that stack instead of the upper layer one?