You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 22, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 22, 2026. It is now read-only.
[BUG] Upgrade from v1.30.1 to v1.32.0 causing No export named ${App}-ArtifactKey found #5472
We have static website deployed using copilot. Today we update the copilot cli to v1.32.0 and we unable to deploy again.
Log:
copilot svc deploy --app myapp --name app --env development
- Updating the infrastructure for stack myapp-development-app [update rollback complete] [12.4s]
No export named myapp-ArtifactKey found
- Request and validate the certificate for your Static Site [not started]
- A CloudFront distribution for global content delivery [not started]
- An IAM Role for the state machine that moves source files to the S3 bucket [not started]
- A state machine that moves source files to the S3 bucket [not started]
- Add A-records for your Static Site alias [not started]
- A custom resource that starts the process of moving files to the S3 bucket [not started]
- An IAM Role for the lambda that starts the process of moving files to the S3 bucket [not started]
- A lambda that starts the process of moving files to the S3 bucket [not started]
â deploy service app to environment development: deploy service: stack myapp-development-app did not complete successfully and exited with status UPDATE_ROLLBACK_COMPLETE
@sumar-triniti I'm sorry that you are facing issue after upgrading! It is true that static site only started using the app-level artifact key from v1.32.0; however, what's baffling is that the said key - myapp-ArtifactKey should be always exported.
Can you take a look at a stack named "Stackset-myapp-infrastructure-", from the same region as "development" environment, then go to the "Outputs" tab, see if you can find something like this:
Thanks for sharing the information. The last bit is extremely helpful!
I can confirm that this is a bug from v1.32.0. From https://github.com/aws/copilot-cli/pull/5329/files, the static site's CopyAssetsStateMachineRole role stated having the permission to decrypt the KMS key stored in the app account. However, CFN import doesn't work for cross account.
I am testing a workaround before I suggest it to you! Thanks for the patience.
Another issue that might related. service package command is not work:
copilot-linux-amd64-v1.32.0 svc package --name app --env production
â generate workload app template against environment production: override template: invalid template: yaml: line 326: mapping values are not allowed in this context
Activity
Lou1415926 commentedon Nov 14, 2023
@sumar-triniti I'm sorry that you are facing issue after upgrading! It is true that static site only started using the app-level artifact key from v1.32.0; however, what's baffling is that the said key -
myapp-ArtifactKeyshould be always exported.Can you take a look at a stack named "Stackset-myapp-infrastructure-", from the same region as "development" environment, then go to the "Outputs" tab, see if you can find something like this:

sumar-triniti commentedon Nov 15, 2023
Hi @Lou1415926 here is my 'StackSet-myapp-infrastructure-' outputs:

Another details about our infrastructure: we have separated aws account:
Stackset-myapp-infrastructure- is at shared account, and all workload is at dev/stag/prod account.
Lou1415926 commentedon Nov 17, 2023
Thanks for sharing the information. The last bit is extremely helpful!
I can confirm that this is a bug from v1.32.0. From https://github.com/aws/copilot-cli/pull/5329/files, the static site's
CopyAssetsStateMachineRolerole stated having the permission to decrypt the KMS key stored in the app account. However, CFN import doesn't work for cross account.I am testing a workaround before I suggest it to you! Thanks for the patience.
sumar-triniti commentedon Nov 17, 2023
I am glad to hear that you already figured out the problem and testing a workaround. Thank you
Lou1415926 commentedon Nov 17, 2023
Okay! To unblock you for now, you can use this YAML patch for your static site:
sumar-triniti commentedon Nov 20, 2023
Tested the workaround, i can confirm it work i can deploy existing static site app and new static site app.
Thanks
sumar-triniti commentedon Nov 20, 2023
Another issue that might related. service package command is not work:
That happen with any override, for example
KollaAdithya commentedon Nov 20, 2023
Hey @sumar-triniti
I am able to reproduce the issue. Thanks for reporting the bug
chore: add quotes to fix the invalid template for svc package for staâĶ
iamhopaul123 commentedon Dec 13, 2023
Hello! The fix is now released in v1.32.1: https://github.com/aws/copilot-cli/releases/tag/v1.32.1