Secrets usage is not documented properly and incredibly confusing
### Before opening, please confirm: - [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md). - [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+). - [X] I have removed any sensitive information from my code snippets and submission. ### Amplify Hosting feature Build settings, Deployments, Environment variables, SSR ### Is your feature request related to a problem? Please describe: AWS Amplify Gen2 console has secrets section and following documentation page about how to use them: - https://docs.amplify.aws/react/deploy-and-host/fullstack-branching/secrets-and-vars/ However, it's way more confusing that it might look from the first glance. #### Frontend build time secrets 1. Documentation says that secrets created through AWS Amplify Gen2 console are stored under the `/amplify/<app-id>/<branch-name>/<secret-name>`: <img width="512" alt="Screenshot 2024-11-18 at 19 10 13" src="https://github.com/user-attachments/assets/8127ad20-9aae-472c-a38f-efe039c9b1f1"> - But in reality they are stored under the under the path like `/amplify/<app-id>/<branch-name>-branch-<some-unknown-id>/<secret-name>`, so amplify is failing to load them in Build Time:: ``` 2024-11-08T18:50:07.430Z [INFO]: ---- Setting Up SSM Secrets ---- 2024-11-08T18:50:07.430Z [INFO]: SSM params {"Path":"/amplify/<app_i
Posted by taraspos on Nov 8, 2024, 7:27 PM
Tags
Related issues
- 2026 - Microsoft Office 365
- [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
- Gamut mapping
- [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
- [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
- [BUG]: infinite loading of videos
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (SaaS)
2026 - Microsoft Office 365
[Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
Gamut mapping
[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
[Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
[BUG]: infinite loading of videos
Restore GPT-5.6 Sol’s 372k Codex context window, or provide an opt-in setting
Codex Desktop for macOS repeatedly triggers `syspolicyd` / `trustd` CPU and memory runaway
Secrets usage is not documented properly and incredibly confusing
### Before opening, please confirm: - [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md). - [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+). - [X] I have removed any sensitive information from my code snippets and submission. ### Amplify Hosting feature Build settings, Deployments, Environment variables, SSR ### Is your feature request related to a problem? Please describe: AWS Amplify Gen2 console has secrets section and following documentation page about how to use them: - https://docs.amplify.aws/react/deploy-and-host/fullstack-branching/secrets-and-vars/ However, it's way more confusing that it might look from the first glance. #### Frontend build time secrets 1. Documentation says that secrets created through AWS Amplify Gen2 console are stored under the `/amplify/<app-id>/<branch-name>/<secret-name>`: <img width="512" alt="Screenshot 2024-11-18 at 19 10 13" src="https://github.com/user-attachments/assets/8127ad20-9aae-472c-a38f-efe039c9b1f1"> - But in reality they are stored under the under the path like `/amplify/<app-id>/<branch-name>-branch-<some-unknown-id>/<secret-name>`, so amplify is failing to load them in Build Time:: ``` 2024-11-08T18:50:07.430Z [INFO]: ---- Setting Up SSM Secrets ---- 2024-11-08T18:50:07.430Z [INFO]: SSM params {"Path":"/amplify/<app_i
Comments (0)
No comments yet. Start the discussion.