cdk deploy: getting error while deploying amplify exported backend #25970
Labels
@aws-cdk/aws-amplify
Related to AWS Amplify
bug
This issue is a bug.
effort/medium
Medium work item – several days of effort
p2
response-requested
Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Describe the bug
I've a amplify application which I have exported the backend using amplify export --out command. I'm trying to import this backend in aws-cdk application using @aws-amplify/cdk-exported-backend package.
When deploying the stack I am getting error at a point when zip file containing lambda build code is getting copied to s3 bucket to internal temporary location.
Expected Behavior
stack should be deployed in the mentioned region.
Current Behavior
getting error Deployment failed: Error: The stack named amplify-agapp-rstest38-94843 failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE: Received response status [FAILED] from custom resource. Message returned: Command '['/opt/awscli/aws', 's3', 'cp', 's3://cdk-hnb659fds-assets-557967369114-us-east-2/a388ded915253af1249fb0de1b9356cd38a6e6e8e5a655bec3a64141029330a7.zip', '/tmp/tmpbbabcyjo/c74bb405-123b-400f-a8a1-03c294329684']' died with <Signals.SIGKILL: 9>. (RequestId: fb1d9ce9-9dd8-4a86-ab35-d28ae9b139f1)
at FullCloudFormationDeployment.monitorDeployment (C:\Users\kaus4624\AppData\Roaming\npm\node_modules\aws-cdk\lib\index.js:403:10236)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Object.deployStack2 [as deployStack] (C:\Users\kaus4624\AppData\Roaming\npm\node_modules\aws-cdk\lib\index.js:406:152469)
at async C:\Users\kaus4624\AppData\Roaming\npm\node_modules\aws-cdk\lib\index.js:406:136265
Reproduction Steps
I'm getting below error:
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.83.1 (build 006b542)
Framework Version
No response
Node.js Version
16.16.0
OS
linux
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: