CDK teams struggle to clean up generated and deployed resources
AWS CDK users report cleanup friction both in local output directories, where generated asset folders can consume gigabytes, and in AWS, where pipeline-created stacks and bootstrap resources are hard to remove together. The evidence describes manual console and CLI cleanup, plus custom flags and wrapper scripts to identify stacks. These signals are from 2018–2020, so the current state of the tooling and demand should be validated before building.
For AWS CDK developers and infrastructure teams. Mentioned from Oct 2018 to Oct 2020 on GitHub.
5 different people described this problem in 3 separate discussions.
- Indie fit
- 2.0/10
- Pain
- 6.0/10
- Frequency
- 6.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.
Each asset folder is around 100 MB for me, so this quickly adds up to many GB of data. Here is a screenshot of it accumulating assets again after the last time I cleaned it out manually
Track all application stacks (for instance by tag) and delete them by a wrapping application/shell script? I thought to select all application-stacks via Tag and delete via aws cli command from a shell script. Is there a more "beautiful" way?
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 3 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks