Skip to content
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 Init just returns 🛑 Failed to get profile credentials #13237

Closed
qwikag opened this issue Sep 19, 2023 · 5 comments
Closed

Amplify Init just returns 🛑 Failed to get profile credentials #13237

qwikag opened this issue Sep 19, 2023 · 5 comments
Labels
bug Something isn't working duplicate If marked with duplicate, issue will be closed & original will be added for traceability platform Issues tied to the general CLI platform

Comments

@qwikag
Copy link

qwikag commented Sep 19, 2023

amplify init

just returns 🛑 Failed to get profile credentials

This needs to be better documented within the tutorial/guide.

@reesscot reesscot transferred this issue from aws-amplify/docs Sep 19, 2023
@reesscot
Copy link

Transferring to CLI repo, as this seems to be a CLI issue

@josefaidt
Copy link
Contributor

Hey @qwikag 👋 would you mind porting this over to our bug template? This will help us gather additional context around the issue you are experiencing to help effectively diagnose.

@josefaidt josefaidt added pending-response Issue is pending response from the issue author pending-triage Issue is pending triage labels Sep 19, 2023
@qwikag
Copy link
Author

qwikag commented Sep 19, 2023

Hey @josefaidt ,
The problem is not the CLI Auth, the problem is the document does not advise how to use the CLI Auth Properly.
So yes it is a combination of the 2, yes CLI AUth is overly complex and not straight forward
There are multiple ways to do it to get a success.
But once it fails a person easily goes looking for the many solutions and then ends up mixing up the solutions create a complex mess of attributes,
So primarily this is a documentation issue, that needs its own place in the prerequisites or the like.
For the noob that is a nightmare. On my third time creating a project I still ran into hours of issues.

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Sep 19, 2023
@josefaidt
Copy link
Contributor

Hey @qwikag apologies for the delay here, and sorry to hear of the rough experience. While the CLI continues to improve its auth flow I will be sure to update the relevant documentation. Please note the known bug with AWS IAM Identity Center/SSO, which I believe we chatted about in another issue. I'll close this in favor of tracking the existing item #4488

@josefaidt josefaidt added bug Something isn't working platform Issues tied to the general CLI platform duplicate If marked with duplicate, issue will be closed & original will be added for traceability and removed pending-triage Issue is pending triage labels Oct 3, 2023
@github-actions
Copy link

github-actions bot commented Oct 3, 2023

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate If marked with duplicate, issue will be closed & original will be added for traceability platform Issues tied to the general CLI platform
Projects
None yet
Development

No branches or pull requests

3 participants