aws / aws/aws-toolkit-vscode

startup: extension fails if ~/.aws/config is missing

Open
#3,843 3 comments 0 reactions 0 assignees View on GitHub
auth-credentials bug
Dominant language
TypeScript
Stars
2k
Forks
807
Avg merge
10h 12m
Merged PRs (30d)
7

Description

## Problem

I have

> Error running command aws.login: command 'aws.login' not found. This is likely caused by the extension that contributes aws.login.

after installing the AWS toolkit extension and clicking on "Connect to AWS"

![image](https://github.com/aws/aws-toolkit-vscode/assets/93609277/87c26b7f-b39c-4c21-8c34-3d16ff751e59)
![image](https://github.com/aws/aws-toolkit-vscode/assets/93609277/5b39e606-ad90-4466-bb7d-2587c20cc044)

## Steps to reproduce the issue

## Expected behavior

I should be able to connect to an IAM role after installing the extension.

## System details (run the `AWS: About Toolkit` command)

- OS: MacOS Ventura 13.5.2
- Visual Studio Code version: 1.82.2 (Universal)
- AWS Toolkit version: v1.90.0
- AWS CLI: installed at `/usr/local/bin/aws`: `aws-cli/2.3.5 Python/3.8.8 Darwin/22.6.0 exe/x86_64`

Contributor guide

Open the contributing guide

Research direction

Reproduce the startup failure with ~/.aws/config absent, using the listed AWS Toolkit and VS Code versions if available. Trace the extension startup and “Connect to AWS” entry point to determine why aws.login is not registered; done means the command is available and connecting to an IAM role succeeds without that file.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
authentication, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.