AWS developers struggle to use SSO credentials across dev tools
In reports from 2020–2022, developers describe AWS SSO credentials working inconsistently across tools: Amplify deployments could use the wrong default account, while a Postman user had to generate and enter temporary credentials manually. Workarounds were tool-specific and could be fragile; one Amplify user reported deleting the project's `amplify` directory while trying another approach. The SAML/SCIM integration issue is a different problem and is not evidence for this opportunity.
For AWS developers and platform engineers using multiple accounts. Mentioned from Mar 2020 to Jul 2024 on GitHub and Hacker News.
6 different people described this problem in 4 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.0/10
- Frequency
- 7.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Issue: multiple profiles not working or amplify ends up publishing in the wrong (default) account
I tried another way but I also had problems. You must delete the "amplify" directory of your project
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks