codepipeline-actions: CloudFormationCreateUpdateStackAction fails when lambda requires assets #29776
Labels
@aws-cdk/aws-codepipeline
Related to AWS CodePipeline
@aws-cdk/aws-codepipeline-actions
bug
This issue is a bug.
documentation
This is a problem with documentation.
effort/medium
Medium work item – several days of effort
p3
Describe the issue
I have a few stacks (ServiceStack,AuthenticationStack, and DataStorageStack). All of which work when deployed locally from the CLI. I decided to try and create a simple CICD pipeline using the
Pipeline
construct from theaws-cdk-lib/aws-codepipeline
module. A simple github source to main, along with a simple build step (npm ci, cdk synth). I then use thecdk.out
generated in an artifact to performactions
specifically theCloudFormationCreateUpdateStackAction
on the stacks (essentially update them). Below is the code for thePipelineStack
:The
Authorization_Update
stage fails with the error:Resource handler returned message: "Error occurred while GetObject. S3 Error Code: NoSuchKey. S3 Error Message: The specified key does not exist. (Service: Lambda, Status Code: 400)"
I did check the S3 bucket and the
asset.zip
file found in the template was there. I don't know if there is any other steps I need to do on my part.I checked the documentation and couldn't find anywhere that suggested whether I should enabled any pipeline service principles access to the lambdas or if there were other parameters (
selfMutating
doesn't seem to be an option in this v2 version of code pipelines). I may be lost a little as to what this entails.I've looked through codepipeline module and the CloudFormationCreateUpdateStackAction which seemed extra lean. Any guidance is appreciated.
Links
The text was updated successfully, but these errors were encountered: