search

aws / aws-toolkit-vscode

Amazon Q, CodeCatalyst, Local Lambda debug, SAM/CFN syntax, ECS Terminal, AWS resources
https://marketplace.visualstudio.com/items?itemName=AmazonWebServices.amazon-q-vscode
Apache License 2.0
1.47k stars 408 forks source link

Error: Connection does not exists #3337

Closed 0xD8C4A475 closed 1 year ago

0xD8C4A475 commented 1 year ago

Problem

No connect

Steps to reproduce the issue

Try connect, login on website, grant acces, but VSCode does nothing

Expected behavior

Connected?

System details (run the AWS: About Toolkit command)

2023-04-17 09:40:15 [INFO]: OS: Windows_NT x64 10.0.19044 2023-04-17 09:40:15 [INFO]: Visual Studio Code extension host: 1.76.1 2023-04-17 09:40:15 [INFO]: AWS Toolkit: 1.68.0 2023-04-17 09:40:15 [INFO]: node: 16.14.2 2023-04-17 09:40:15 [INFO]: electron: 19.1.11

ErrorLog:

2023-04-17 09:40:15 [ERROR]: log level: info 2023-04-17 09:40:15 [INFO]: Retrieving AWS endpoint data 2023-04-17 09:40:15 [INFO]: OS: Windows_NT x64 10.0.19044 2023-04-17 09:40:15 [INFO]: Visual Studio Code extension host: 1.76.1 2023-04-17 09:40:15 [INFO]: AWS Toolkit: 1.68.0 2023-04-17 09:40:15 [INFO]: node: 16.14.2 2023-04-17 09:40:15 [INFO]: electron: 19.1.11 2023-04-17 09:40:15 [WARN]: AwsContext: no default region in credentials profile, falling back to us-east-1: 2023-04-17 09:40:24 [WARN]: auth: failed to auto-connect using "ec2:instance": Error: Connection does not exist: ec2:instance 2023-04-17 09:40:24 [WARN]: auth: failed to auto-connect using "ecs:instance": Error: Connection does not exist: ecs:instance 2023-04-17 09:40:24 [WARN]: auth: failed to auto-connect using "profile:default": Error: Connection does not exist: profile:default

justinmk3 commented 1 year ago

Try connect, login on website, grant acces, but VSCode does nothing

Are you trying to use CodeWhisperer or CodeCatalyst? If CodeWhisperer, did you open a code file (what kind...?) and try to write code? More details are needed before I can help.

Thanks for the logs. Can you set log-level to "debug" and post the resulting logs (check that private info is removed)?

  1. In VSCode settings, ensure that "aws log level" is "debug".
  2. Perform the steps to reproduce the issue.
  3. Use the AWS: View Toolkit Logs command to get the logs.
justinmk3 commented 1 year ago

AWS Toolkit 1.71 includes several improvements to authenticate logic.

AWS Toolkit 1.72 will include further improvements. https://github.com/aws/aws-toolkit-vscode/issues/3403