WSL: Cannot connect: login: failed ... Socket is closed
Open
auth-credentials
guidance
needs-response
platform:windows
platform:wsl
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 807
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 7
Description
**Desktop (please complete the following information):**
- OS: Windows 10
- aws-cli/1.22.73 Python/3.8.10 Linux/5.10.102.1-microsoft-standard-WSL2 botocore/1.24.18
- VS Code version: 1.66.2
- AWS Toolkit extension version: 1.37.0
**Question**
Cannot connect to AWS with AWS Toolkit
[ERROR]: login: failed to connect with "profile:PROFILE_NAME": Socket is closed
Contributor guide
Research direction
Start by reproducing the failed AWS Toolkit connection in the reported Windows 10 WSL2, VS Code 1.66.2, and extension 1.37.0 environment, then trace the login path that reports “Socket is closed.” Done means identifying the failure cause and confirming that the affected profile can connect successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript, vscode
- Domain
- authentication, cloud, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100