AWS users struggle to organize growing profile configurations
AWS users with many personal, work, and client accounts find the single `~/.aws/config` file unwieldy; one user described a customer with thousands of accounts. Because the CLI does not load a directory of config fragments, users must manage a large file or maintain separate files and switch between them, making profile changes harder to track.
For AWS practitioners and cloud administrators managing many account profiles. Mentioned from Aug 2016 to May 2026 on GitHub.
7 different people described this problem in 5 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.0/10
- Frequency
- 7.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Recently dealt with a customer with a few thousand AWS accounts. My kingdom for this feature!
My ~/.aws/config file is massive. I have a proliferation of personal accounts, work accounts, and each client grants me a profile within dozens of accounts as well
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 7 more quotes from people who have this problem
- Current workarounds, existing solutions and risks