Environment variables from SSM Parameter Store or Secrets Manager

It seems currently the only way to set environment variables on an Amplify app is by providing a plaintext value. It would be really useful to provide them from Parameter Store or Secrets Manager. I have an app which requires private npm authentication during the build stage. Currently I have to provide the GitHub personal access token to Amplify as a plaintext value. I also have to remember to update it here when I regenerate the token.

No files or tests are identified in the issue. Start by locating the Amplify Hosting build-environment entry point and the AWS Parameter Store or Secrets Manager integration surface; done means build-time environment variables can use those managed values instead of requiring plaintext tokens and can reflect token rotation.

Written by the indexing model from the issue text.