Command for diagnosing common issues
- Dominant language
- Python
- Stars
- 17.3k
- Forks
- 4.6k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 13
Description
### Describe the feature
AWS SSO provides the opportunity to do more thorough debugging of a user's configuration when something isn't working. Debugging access issues can be done using the `--debug` flag, but it's a ton of information and not necessarily straightforward to understand.
### Use Case
As a user, there are many things that can go wrong. I may have AWS SSO configured correctly, but I may not have access to the account and/or role in my configuration. My access token may be expired. My access token cache file may have the wrong file permissions (I have seen scripts run as root that perform `aws sso login`, which then regular commands can't read the token written there).
Having this diagnostic built into the AWS CLI enables support teams to ask a user to provide the output of it and receive comprehensive information about why the user may be experiencing the problem they are having.
### Proposed Solution
The model for this is [`aws-sso-util check`](https://github.com/benkehoe/aws-sso-util/blob/master/docs/check.md), which attempts to provide a comprehensive but easy to understand summary of the user's setup, including information like cache file ownership if it's a problem.
### Other Information
_No response_
### Acknowledgements
- [X] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CLI version used
N/A
### Environment details (OS name and version, etc.)
N/A
Contributor guide
Assessment
This issue has not been assessed yet.