towardsthecloud / towardsthecloud/cloudburn
Detect empty Route 53 hosted zones
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 371
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 63
Description
What
Detect Route 53 hosted zones that contain no records beyond the default SOA and NS records.
Why
Hosted zones incur a recurring charge and are easy to leave behind after records or environments are removed. Ignoring the default records provides a direct, low-noise orphan signal.
Details
- Join hosted-zone metadata with paginated record-set discovery.
- Flag only zones with no non-default records, and report public or private zone type, VPC associations, creation evidence when available, and monthly cost context.
- Treat private zones with VPC associations as review findings rather than automatic deletion candidates.
- Exclude zones when record discovery is incomplete or access is denied.
- Discovery only. Continue the
CLDBRN-AWS-ROUTE53-Nsequence.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CLDBRN-AWS-ROUTE53-N sequence and the existing hosted-zone metadata and paginated record-set discovery entry points. Trace how discovery results are represented, then define completion around flagging zones with only default SOA and NS records, reporting the requested context, treating associated private zones as review findings, and excluding incomplete or denied discoveries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100