- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Without further context around the run which failed on Lambda, it is difficult to speculate, however based on the naming, it looks like it may be part of the stack which you are trying to deploy, as it seems to match the style of CDK-generated names.
As for the permissions, CDK normally creates a deployment role in your account as part of the bootstrapping process. I have included a link to the details of this role in the bootstrapping template (1). One potential option here is to specify this role in your CDK CLI call by passing the -r
or --role-arn
parameter with that role (2). If you are experiencing this issue in an account or region that has not been bootstrapped, then you may just need to bootstrap the account in order to have this deployment role (3)
I hope this helps! If you need more assistance with this, I would encourage you to open a support case with CDK so that we can have a more hands-on look at the current configuration, and can provide more concise advice, securely and one-on-one.
(2) https://docs.aws.amazon.com/cdk/v2/guide/cli.html#cli-ref : AWS CDK Toolkit (<code class="code">cdk</code> command) - Toolkit reference
(3) https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping.html : Bootstrapping
I added to my Build project service role the following missing permissions and it works :
1 - S3:listObjects
2- AWSLambdaRole to have the permission to lambda:InvokeFunction
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr