-
What is the current best practice for deploying multiple CDK v2 apps into the same account using CI? Previously using v1 we created app-specific roles which our CI tool assumed and apps could be deployed with the exact required permissions. But with the v2 it appears that it always wants to assume and use roles the bootstrap created ignoring the credentials available in the environment. I know I can create a custom policy and pass that into the bootstrap command with The docs are not terribly clear on how to handle this situation. There appears to be a couple of options like:
None of these are as easy as the v1 situation of 'just make a role with minimum permissions per app and assume it before calling What is the best way to do this in a CDK v2 world? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
If you use it via
|
Beta Was this translation helpful? Give feedback.
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
If you use it via
const app = new App({ defaultStackSynthesizer: new CliCredentialsStackSynthesizer() });
and grant the current role the right permissions to write into the CDK asset bucket, create and manage CF stacks, etc. then it actually works quite quickly. We created a role with the following inline permission: