-
Notifications
You must be signed in to change notification settings - Fork 826
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
Amplify CLI does work with AWS SSO credentials #6338
Comments
@zhiweil can you check if you have credentials for that profile listed in |
Closing this as a dupe of #4488. We don't support this out of the box currently but you can check the thread in that issue for a workaround that may work for you. |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Describe the bug
The amplify CLI does not work with the AWS profile generated by AWS Single Sign On. I received a error saying "Could not initialize 'some-amplify-env': Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1"
The Amplify CLI version is: 4.41.0
NodeJS version is: 15.5.1
To Reproduce
I'm setting up a laptop to work with an existing Amplify environment. AWS profile is created in by AWS single sign on.
Run "aws sso login --profile zhiwei-dev" and test the new credential by CLI "aws s3 ls --profile zhiwei-dev". The call succeeds.
Clone an existing CodeCommit GIT repo by the following command and it succeeds.
Expected behavior
I expect Amplify CLI would work with credentials generated by AWS SSO as this is a fairly common practice under a multi-account environment.
The text was updated successfully, but these errors were encountered: