Kethan sai

Marking this as feature request.

Hey,👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂

Hey,👋 thanks for raising this! I'm going to transfer this over to our data repository for better assistance 🙂

Hey @PatrickNies, thank you for reaching out. You should be able to run `aws configure` using aws cli which should re-prompt to update your existing credentials. Additionally, the AWS CLI...

Marking this as feature request to support updating existing profile configuration on `npx ampx configure profile`.

Hey @sph94, thank you for reaching out. The information is currently documented on https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html#environment-secrets Transferring to the backend repository and marking this for improvements.

Hey @adeldueast, thank you for reaching out. Amplify Studio creates a full access role with `Adminstrator-Amplify` and `full-access` managed policy. We may need to add a inline policy with a...

Hey, thank you for reaching out. Amplify backend secrets are currently not supported on custom functions.  For functions using custom runtimes I would suggest using [AWS SDK SSMClient](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ssm.html) directly...

@cookiejest you will not be able to pass in Amplify generated secrets via the environment variables but you will need to create a custom SSM parameter and then use the...

Following up on this issue. Do let us know if you require any additional information on this.