-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Can't deploy because of Secrets issue #5752
Comments
This has been reported in #5732. You need to give the full ARN of the secret, not just its name. |
Same error when using the full ARN. |
Tried with full ARN
|
@apassy remove the _ and any - in the last segment of your secret. @Lou1415926 we just had this issue where our copilot services could not access secrets where the last segment had a hyphen. It appears if the hyphen is in a previous segment, but not the ending segment, it's fine such as: No matter what you'll get an error about accessing the secret. |
I think this is still a bug, all my secrets are working fine in my first environment but now I'm seeing this error when trying to deploy to a new environment |
@ssyberg can you check if the secrets are properly tagged with |
It was totally the tagging, I missed that sentence in the docs! |
Other Closed Issues related to tagging.
Description:
I'm trying to deploy a service that I previously deployed just fine, but I added a secrets section to the manifest, and now it's failing.
Details:
Copilot ver: 1.33.1
running on Windows 11
Load-balanced web app
Additional manifest lines:
Error:
Secrets are tagged with the copilot-application and copilot-environment and those match what I'm using.
Expected result:
expected successful deployment
The text was updated successfully, but these errors were encountered: