Skip to content

docs(blog): add draft for pruning unused resources post - #5

Open
nitrocode wants to merge 1 commit into
mainfrom
blog/pruning-unused-resources
Open

docs(blog): add draft for pruning unused resources post#5
nitrocode wants to merge 1 commit into
mainfrom
blog/pruning-unused-resources

Conversation

@nitrocode

Copy link
Copy Markdown
Owner

what

  • Adds a draft blog post on deleting unused AWS resources via a Cloud Custodian (c7n-org) pipeline that runs in a GitHub Action on an hourly cron.
  • The post lives in _drafts/ so Jekyll does not deploy it; preview locally with bundle exec jekyll serve --drafts.

why

  • Captures a real cleanup engagement (~10,000 resources removed across 8 types) as a reusable narrative for this site.
  • Demonstrates the state-machine + rate-limited-action pattern in c7n-org (tag, resurrect, quarantine, delete) so a reader can adapt it.
  • Covers the IAM deep dive (CSPM blind spot on stale trust policies), the audit side-benefit (shorter administrator list), and an estimated cost-impact table.

references

🌙 Generated with Claude Code on opus[1m].

Multi-resource cleanup post covering the c7n-org pipeline. Topics:
4-stage state machine (tag, resurrect, quarantine, delete) running on
an hourly GitHub Action cron, rate-limited deletion, eight resource
types (IAM roles, security groups, EIPs, EBS volumes, RDS instances,
ELBs, snapshots, NAT gateways), and an estimated cost-impact table.
Includes a mermaid state diagram, an IAM role deep dive, and an audit
side-benefit subsection.

Co-Authored-By: AI pair (📡 RB's pair) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant