Cloud teams struggle to find and import existing resources
Cloud administrators and infrastructure engineers need to locate resources across many accounts, subscriptions, and regions, then manage them through infrastructure as code. Existing portal searches and scripts can be cumbersome or fragile at scale, while data-source and manual import workflows can be slow and verbose. Teams also want safer automation when a resource may already exist—or may need to be created.
For cloud infrastructure teams. Mentioned from Aug 2023 to May 2026 on GitHub and Hacker News.
6 different people described this problem in 4 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 7.3/10
- Frequency
- 7.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
If I need to check something across our 5000+ subscriptions looking for a resource is an absolute chore
irusensei on Hacker NewsMar 2024I attempted to use data sources and complex scripting with OpenTofu. However, without a dedicated query command or list resource support, these approaches are either slow, verbose, or do not scale well
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks