Description
Describe the content issue:
You probably need a software change to the CLI to implement a long-term solution, but customers should be able to plug in temporary credentials, a credential process, or Cognito identity pools to populate credentials to the Amplify environment. There's even a screenshot on this page that shows a warning in the IAM console against the use of long-term credentials.
If this process just populates .aws\credentials on the local machine, I recommend providing general guidance about populating credentials to your dev environment and linking out to https://docs.aws.amazon.com/IAM/latest/UserGuide/security-creds.html#sec-access-keys-and-secret-access-keys . At the very least, this could start with a note that says "The following process describes how to use amplify configure to populate your development environment with long-term credentials. As a best practice, populate your development environment with temporary credentials. See "AWS security credentials" in the AWS Identity and Access Management User Guide."
URL page where content issue is:
https://docs.amplify.aws/cli/start/install/#configure-the-amplify-cli