upgrade to 10.8.1 returning failed to get profile credentials #12174

adcanis · 2023-03-04T20:01:16Z

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

19.6.0

Amplify CLI Version

10.8.2

What operating system are you using?

mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

no

Describe the bug

upgrade to 10.8.2 fails to get profile credentials when performing amplify task. Sends Authorization request multiple times despite currently being logged in before failing with error:

"Failed to get profile credentials. Unexpected token A in JSON at position 0"

Expected behavior

should allow amplify commands the same as v10.8.0

Reproduction steps

aws-vault exec
authenticate
update schema
amplify push -y

Project Identifier

9004eca0-6404-4a91-9fae-e5a8474cb213

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
I have removed any sensitive information from my code snippets and submission.

The text was updated successfully, but these errors were encountered:

adcanis · 2023-03-06T17:01:20Z

Seems to be an issue with pushing. I was able to pull, but it still kicked me to authorization 3 times

josefaidt · 2023-03-06T17:07:35Z

Hey @adcanis 👋 thanks for raising this! Can you confirm your Amplify CLI version? The issue description mentions 10.8.2 though the latest is 10.8.1

adcanis · 2023-03-06T17:08:37Z

sorry yes your right. 10.8.1 and was working on 10.8.0

josefaidt · 2023-03-06T17:10:04Z

Ah no worries just wanted to clarify 🙂 do you only experience this issue in this one project or are you able to execute commands outside the project?

adcanis · 2023-03-06T17:11:04Z

This is the only project using SSO credentials.
EDIT I'll also add my config and credentials file:

Config

[profile <Profile name>]
sso_start_url = https://******.awsapps.com/start
sso_region = ca-central-1  
sso_account_id = **********
sso_role_name = *********
credential_process = aws sso login --profile <Profile name>
region = ca-central-1
output = json

Credentials

[<Profile name>]
aws_access_key_id=********************
aws_secret_access_key=***********************
aws_session_token=********************************

josefaidt · 2023-03-06T17:12:21Z

Thanks for clarifying @adcanis , I'm going to take a further look at this one 🙂

josefaidt · 2023-03-06T17:34:02Z

Hey @adcanis while we investigate this further can you run the same command with --debug to print the stack trace?

adcanis · 2023-03-06T17:37:17Z

Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

BackendPullFault: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    at syncCurrentCloudBackend (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/push.js:59:15)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Object.run (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/push.js:73:5)
    at async Object.executeAmplifyCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:181:9)
    at async executePluginModuleCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:144:5)
    at async executeCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:42:9)
    at async Object.run (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:120:5)

Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
Error: connect EHOSTDOWN 169.254.169.254:80 - Local (192.168.1.141:50654)
    at internalConnect (net.js:934:16)
    at defaultTriggerAsyncIdScope (internal/async_hooks.js:452:18)
    at net.js:1022:9
    at processTicksAndRejections (internal/process/task_queues.js:77:11)

Session Identifier: b7bf36f2-a7eb-45fa-bda9-c18dc8f0eeb2

josefaidt · 2023-03-06T20:05:13Z

Hey @adcanis thanks for pasting that output. I have not been able to reproduce this issue with just credentials on environment variables. Does aws-vault create a config or credentials file at ~/.aws/?

as a note, this may be fixed with #12139

adcanis · 2023-03-06T20:16:16Z

@josefaidt aws-vault doesn't create a new config file or credentials file. Instead, it stores the temporary session credentials in memory. This has worked in multiple projects. I've also cleared aws-vault and used aws sso login --profile <profile name> and received the same multiple authentication pages throughout the push process before returning the same error

when I run aws sso login --profile <profile name> i get an additional error:

Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1

josefaidt · 2023-03-06T20:19:26Z

Hey @adcanis can you paste the output of amplify/.config/local-aws-info.json?

adcanis · 2023-03-06T20:20:55Z

{
  "dev": {
    "configLevel": "project",
    "useProfile": true,
    "profileName": "account-sso-dev"
  }
}

adcanis · 2023-03-06T21:19:13Z

@josefaidt if it helps. The issue seems to be related to my API. I've re-pulled the backend, making a small change to my Lambda and amplify push was successful. The API fails with error

Failed to get profile credentials. Unexpected token A in JSON at position 0

josefaidt · 2023-03-06T23:27:18Z

Hey @adcanis thanks for posting that! Can you try running the command with the AWS_SDK_LOAD_CONFIG env var set to 1?

AWS_SDK_LOAD_CONFIG=1 amplify push -y

adcanis · 2023-03-07T00:31:15Z

@josefaidt same thing

josefaidt · 2023-03-22T21:50:33Z

Captured stack trace output for debugging

ProfileConfigurationError: Failed to get profile credentials
    at loadConfigurationForEnv (/snapshot/repo/build/node_modules/@aws-amplify/amplify-provider-awscloudformation/lib/configuration-manager.js:777:13)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Object.loadConfiguration (/snapshot/repo/build/node_modules/@aws-amplify/amplify-provider-awscloudformation/lib/configuration-manager.js:718:18)
    at async Object.configureWithCreds (/snapshot/repo/build/node_modules/@aws-amplify/amplify-provider-awscloudformation/lib/aws-utils/aws.js:34:18)
    at async Object.getConfiguredAWSClient (/snapshot/repo/build/node_modules/@aws-amplify/amplify-provider-awscloudformation/lib/index.js:281:3)
    at async getAWSClient (/snapshot/repo/build/node_modules/@aws-amplify/amplify-console-hosting/lib/utils/client-factory.js:18:10)
    at async Object.getAmplifyClient (/snapshot/repo/build/node_modules/@aws-amplify/amplify-console-hosting/lib/utils/client-factory.js:4:15)
    at async Object.generateTableContentForApp (/snapshot/repo/build/node_modules/@aws-amplify/amplify-console-hosting/lib/utils/table-utils.js:10:25)
    at async Object.status (/snapshot/repo/build/node_modules/@aws-amplify/amplify-console-hosting/lib/hosting/index.js:164:3)
    at async status (/snapshot/repo/build/node_modules/@aws-amplify/amplify-console-hosting/lib/index.js:29:5)
    at async showAmplifyConsoleHostingStatus (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/status.js:62:13)
    at async Object.run (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/status.js:53:9)
    at async Object.executeAmplifyCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:189:9)
    at async executePluginModuleCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:135:5)
    at async executeCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:33:9)
    at async Object.run (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:117:5)

Unexpected token A in JSON at position 0
ProcessCredentialsProviderFailure: Unexpected token A in JSON at position 0
    at /snapshot/repo/build/node_modules/aws-sdk/lib/credentials/process_credentials.js:142:13
    at ChildProcess.exithandler (child_process.js:374:7)
    at ChildProcess.emit (events.js:400:28)
    at ChildProcess.emit (domain.js:475:12)
    at maybeClose (internal/child_process.js:1088:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:296:5)
⠧ Fetching AWS Amplify Console domains
Session Identifier: 3e45598e-b810-4408-9fd0-bf623bde9788

adcanis · 2023-03-27T18:47:20Z

@josefaidt any luck on this?

josefaidt · 2023-03-27T21:58:30Z

Hey @adcanis the team is actively investigating this issue for a fix

adcanis · 2023-03-28T20:35:59Z

@josefaidt if it helps any, the issue only happens when the account exceeds the 8hr expiration. running aws sso login --profile <> then returns token expired. It is the same issue essentially as this: 7361

github-actions · 2023-03-28T23:47:04Z

⚠️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.

adcanis · 2023-03-29T12:37:49Z

I'm still seeing error "the provided token has expired"
Steps taken:

run aws sso logout
run aws sso login --profile <profile name>
run amplify push -y

josefaidt · 2023-03-29T15:50:25Z

Hey @adcanis this was closed from automation but has not quite been released. I've added pending-release and will circle back shortly!

adcanis · 2023-03-29T15:52:32Z

@josefaidt thanks, I've added a new issue if you'd like to remove it #7789 it may outline the issue a little better

adcanis · 2023-04-13T13:25:38Z

Just a follow up. The issue seems to be with aws sso. When aws sso login --profile <> is ran to login, it does not update the /.aws/credentials with the new AWS Access Key ID, AWS Secret Access Key, AWS Session Token. This throws the error experienced above.

What i've been doing now is logging in, then pasting the new credentials found in Command line or programmatic access and performing the amplify commands after.

OperationalFallacy · 2023-04-17T23:05:22Z

npx amplify --version
11.0.5

I've tried to use amplify first time and immediately ended up on this issue. Dear maintainers, this is the first thing customer sees when interacting with the library. I'm sorry to say this, but it's pretty terrible experience.

Every other web library I've used had flawless initial auth flow (usually oauth2 with GitHub).

pavellazar · 2023-05-16T13:04:56Z

Hi @OperationalFallacy, sorry for late response. I am not able to reproduce the issue using latest Amplify CLI, can you provide more details about the issue you're having?

which command is failing for you? can you provide the stack trace printed when you execute the command with --debug flag?
can you provide a set of steps to reproduce the issue in a newly created project?
can you share with us at [email protected] your ~/.aws/config file, please remove any sensitive information
is your issue with selecting an AWS profile on amplify init or you're experiencing issues with the Social Sign-in Auth flow as described here: https://docs.amplify.aws/lib/auth/social/q/platform/js/

Thank you

pavellazar · 2023-05-22T19:00:18Z

Closing, as we cannot reproduce any longer using latest CLI, if you're still experiencing the issue please create a new issue.

github-actions · 2023-05-22T19:00:43Z

⚠️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.

OperationalFallacy · 2023-06-15T18:19:21Z

Hi @OperationalFallacy, sorry for late response. I am not able to reproduce the issue using latest Amplify CLI, can you provide more details about the issue you're having?

which command is failing for you? can you provide the stack trace printed when you execute the command with --debug flag?

can you provide a set of steps to reproduce the issue in a newly created project?

can you share with us at [email protected] your ~/.aws/config file, please remove any sensitive information

is your issue with selecting an AWS profile on amplify init or you're experiencing issues with the Social Sign-in Auth flow as described here: https://docs.amplify.aws/lib/auth/social/q/platform/js/

Thank you

Here's a full output on a freshly installed amplify package, new project.

amplify init
Note: It is recommended to run this command from the root of your app directory
? Enter a name for the project testapi
The following configuration will be applied:

Project information
| Name: testapi
| Environment: dev
| Default editor: Visual Studio Code
| App type: javascript
| Javascript framework: none
| Source Directory Path: src
| Distribution Directory Path: dist
| Build Command: npm run-script build
| Start Command: npm run-script start

? Initialize the project with the above configuration? No
? Enter a name for the environment dev
? Choose your default editor: Visual Studio Code
✔ Choose the type of app that you're building · javascript
Please tell us about your project
? What javascript framework are you using react
? Source Directory Path:  src
? Distribution Directory Path: build
? Build Command:  npm run-script build
? Start Command: npm run-script start
Using default provider  awscloudformation
? Select the authentication method you want to use: AWS profile

For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

? Please choose the profile you want to use testprofile-sso-dev
🛑 Failed to get profile credentials
Cannot read properties of undefined (reading 'accessKeyId')

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: 83461e3a-9008-4ee5-92ae-8c376a5e103f

There is nothing special about profile, standard SSO

[profile testprofile-sso-dev]
sso_start_url = https://test.awsapps.com/start#/
sso_region = us-east-1
sso_account_id = xxx
sso_role_name = Developer
region = us-east-1
output = json

and its logged in and working properly, I've tried some simple operations like aws s3 ls

thantos · 2023-10-09T19:51:03Z

Same issue as @OperationalFallacy. SSO profile is working for the SDK and CDK.

[profile my-profile]
sso_start_url = https://[redacted].awsapps.com/start
sso_region = us-east-1
sso_account_id = [redacted]
sso_role_name = [redacted]
region = us-east-1

OperationalFallacy · 2023-10-29T16:10:21Z

Amplify team, can you at least fix this error message?

Explain users what config it is, what credentials, and how to fix it.
Also you should explain why do they need to to use AWS_CONFIG_FILE or set AWS_SDK_LOAD_CONFIG=1

It's even more annoying to see this "helpful" message then the broken auth itself.

The auth workflow for local development remains an absolutely terrible experience on the platform.

adcanis added the pending-triage Issue is pending triage label Mar 4, 2023

josefaidt added platform Issues tied to the general CLI platform pending-response Issue is pending response from the issue author and removed pending-triage Issue is pending triage labels Mar 6, 2023

josefaidt added the pending-triage Issue is pending triage label Mar 6, 2023

josefaidt self-assigned this Mar 6, 2023

github-actions bot removed the pending-response Issue is pending response from the issue author label Mar 6, 2023

josefaidt added the investigating This issue is being investigated label Mar 6, 2023

adcanis changed the title ~~upgrade to 10.8.2 returning failed to get profile credentials~~ upgrade to 10.8.1 returning failed to get profile credentials Mar 6, 2023

josefaidt added the pending-response Issue is pending response from the issue author label Mar 6, 2023

github-actions bot removed the pending-response Issue is pending response from the issue author label Mar 6, 2023

josefaidt added the pending-response Issue is pending response from the issue author label Mar 6, 2023

github-actions bot removed the pending-response Issue is pending response from the issue author label Mar 6, 2023

josefaidt added pending-response Issue is pending response from the issue author and removed investigating This issue is being investigated labels Mar 6, 2023

adcanis mentioned this issue Mar 21, 2023

Token expiration and failed login when pusing #12056

Closed

2 tasks

josefaidt mentioned this issue Mar 21, 2023

Pull environmnet on Github workflow #12273

Closed

josefaidt added the p1 label Mar 21, 2023

josefaidt assigned pavellazar Mar 21, 2023

pavellazar mentioned this issue Mar 28, 2023

fix: sso login #12325

Merged

3 tasks

pavellazar linked a pull request Mar 28, 2023 that will close this issue

fix: sso login #12325

Merged

3 tasks

pavellazar closed this as completed in #12325 Mar 28, 2023

This was referenced Mar 29, 2023

Token expiration after re-login aws/aws-cli#7789

Closed

AWS SSO: Failed to get profile credentials #12330

Closed

josefaidt added the pending-release Code has been merged but pending release label Mar 29, 2023

josefaidt reopened this Mar 29, 2023

josefaidt mentioned this issue Apr 17, 2023

Does the Amplify CLI support SSO authentication? #12476

Closed

pavellazar closed this as completed May 22, 2023

restfulhead mentioned this issue Jun 10, 2023

amplify init fails when selecting sso-session entry in profile list: Failed to get profile credentials, Unexpected token A in JSON at position 0 #12777

Open

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

upgrade to 10.8.1 returning failed to get profile credentials #12174

upgrade to 10.8.1 returning failed to get profile credentials #12174

adcanis commented Mar 4, 2023

adcanis commented Mar 6, 2023 •

edited

Loading

josefaidt commented Mar 6, 2023

adcanis commented Mar 6, 2023

josefaidt commented Mar 6, 2023

adcanis commented Mar 6, 2023 •

edited

Loading

josefaidt commented Mar 6, 2023

josefaidt commented Mar 6, 2023

adcanis commented Mar 6, 2023

josefaidt commented Mar 6, 2023

adcanis commented Mar 6, 2023 •

edited

Loading

josefaidt commented Mar 6, 2023

adcanis commented Mar 6, 2023

adcanis commented Mar 6, 2023

josefaidt commented Mar 6, 2023

adcanis commented Mar 7, 2023

josefaidt commented Mar 22, 2023

adcanis commented Mar 27, 2023 •

edited

Loading

josefaidt commented Mar 27, 2023

adcanis commented Mar 28, 2023

github-actions bot commented Mar 28, 2023

adcanis commented Mar 29, 2023

josefaidt commented Mar 29, 2023

adcanis commented Mar 29, 2023

adcanis commented Apr 13, 2023

OperationalFallacy commented Apr 17, 2023

pavellazar commented May 16, 2023

pavellazar commented May 22, 2023

github-actions bot commented May 22, 2023

OperationalFallacy commented Jun 15, 2023

thantos commented Oct 9, 2023 •

edited

Loading

OperationalFallacy commented Oct 29, 2023

upgrade to 10.8.1 returning failed to get profile credentials #12174

upgrade to 10.8.1 returning failed to get profile credentials #12174

Comments

adcanis commented Mar 4, 2023

How did you install the Amplify CLI?

If applicable, what version of Node.js are you using?

Amplify CLI Version

What operating system are you using?

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Describe the bug

Expected behavior

Reproduction steps

Project Identifier

Log output

Additional information

Before submitting, please confirm:

adcanis commented Mar 6, 2023 • edited Loading

josefaidt commented Mar 6, 2023

adcanis commented Mar 6, 2023

josefaidt commented Mar 6, 2023

adcanis commented Mar 6, 2023 • edited Loading

josefaidt commented Mar 6, 2023

josefaidt commented Mar 6, 2023

adcanis commented Mar 6, 2023

josefaidt commented Mar 6, 2023

adcanis commented Mar 6, 2023 • edited Loading

josefaidt commented Mar 6, 2023

adcanis commented Mar 6, 2023

adcanis commented Mar 6, 2023

josefaidt commented Mar 6, 2023

adcanis commented Mar 7, 2023

josefaidt commented Mar 22, 2023

adcanis commented Mar 27, 2023 • edited Loading

josefaidt commented Mar 27, 2023

adcanis commented Mar 28, 2023

github-actions bot commented Mar 28, 2023

⚠️COMMENT VISIBILITY WARNING⚠️

adcanis commented Mar 29, 2023

josefaidt commented Mar 29, 2023

adcanis commented Mar 29, 2023

adcanis commented Apr 13, 2023

OperationalFallacy commented Apr 17, 2023

pavellazar commented May 16, 2023

pavellazar commented May 22, 2023

github-actions bot commented May 22, 2023

⚠️COMMENT VISIBILITY WARNING⚠️

OperationalFallacy commented Jun 15, 2023

thantos commented Oct 9, 2023 • edited Loading

OperationalFallacy commented Oct 29, 2023

adcanis commented Mar 6, 2023 •

edited

Loading

adcanis commented Mar 6, 2023 •

edited

Loading

adcanis commented Mar 6, 2023 •

edited

Loading

adcanis commented Mar 27, 2023 •

edited

Loading

thantos commented Oct 9, 2023 •

edited

Loading