CDK Assembly Garbage Collector - Clean up unused assets in your cdk.out directory, remove locally built Docker images, and delete temporary CDK directories.

cdk-agc is a fast CLI tool that helps you reclaim disk space from AWS CDK builds:

• Clean cdk.out directories: Remove unused assets while protecting referenced files

  • Only deletes unreferenced asset.* directories and files - all other files are automatically protected
  • Protects recently modified files (configurable with -k/--keep-hours)

• Remove locally built Docker images: Clean up orphaned Docker images from CDK builds

  • Automatically removes Docker images associated with deleted asset directories
  • Displays size information for each image and total space to reclaim

• Clean temporary directories (-t/--cleanup-tmp): Delete accumulated temporary CDK directories in $TMPDIR

  • Deletes entire directories
  • Only time-based protection with -k/--keep-hours

This helps optimize storage and streamline CI/CD caching.

• CDK asset directories can grow to multiple GBs over time
• Docker images from CDK builds accumulate in local Docker daemon
• Temporary directories in $TMPDIR accumulate
• Disk space exhaustion from accumulated build artifacts
• Slow CI/CD pipelines due to large cache sizes

cdk-agc provides safe, intelligent cleanup with:

• Reference-based protection: Only removes assets not referenced in *.assets.json files
• Time-based protection: Keeps recent assets for quick rollbacks

# Run directly with npx (no installation needed)
npx cdk-agc

# Or install globally
npm install -g cdk-agc

• Node.js >= 20.0.0

# Default: Clean cdk.out, keeping only referenced assets
npx cdk-agc

# Dry-run: Preview what would be deleted
npx cdk-agc -d

# Verbose: Show detailed operation information
npx cdk-agc -v

# Custom directory (useful for monorepos)
npx cdk-agc -o ./packages/infra/cdk.out

# Keep assets modified within the last 24 hours
npx cdk-agc -k 24

# Clean temporary directories in $TMPDIR
npx cdk-agc -t

cdk-agc only deletes asset.* directories and files that are not actively referenced. All CDK metadata files are always preserved.

• asset.{hash}/ - Unreferenced asset directories
• asset.{hash}.{ext} - Unreferenced asset files (e.g., .txt, .zip)
• Docker images - Local Docker images associated with deleted asset directories
  • Searches for both ECR format ({account}.dkr.ecr.{region}.amazonaws.com/cdk-*:hash) and local format (cdkasset-{hash}:latest)
  • Only removes images for assets that are being deleted

CDK metadata (never deleted):

• manifest.json
• tree.json
• cdk.out
• *.template.json
• *.assets.json
• etc.

asset.* files/directories are protected from deletion if they meet any of these criteria:

1. Active References: Referenced in *.assets.json files
2. Recent Modifications: Modified within the last N hours (when using -k/--keep-hours)

# After switching branches or reverting commits
git checkout feature-branch
npx cdk-agc -k 1  # Keep last hour's assets for quick rollback

# GitHub Actions example
- name: CDK Synth
  run: npx cdk synth

- name: Clean unused assets
  run: npx cdk-agc

- name: Cache CDK output
  uses: actions/cache@v3
  with:
    path: cdk.out
    key: cdk-${{ github.head_ref || github.ref_name }}

# Clean multiple CDK projects
npx cdk-agc -o ./apps/api/cdk.out
npx cdk-agc -o ./apps/web/cdk.out

CDK creates temporary directories in $TMPDIR during synthesis (directories starting with cdk.out, cdk-, or .cdk), which can accumulate over time. Use -t/--cleanup-tmp to reclaim disk space.

Note: This option deletes entire directories. Time-based protection with -k/--keep-hours is the only protection applied.

# Clean all temporary CDK directories (dry-run first)
npx cdk-agc -t -d

# Actually clean them
npx cdk-agc -t

# Protect recent directories (last 24 hours)
npx cdk-agc -t -k 24

By default, cdk-agc uses the docker command to manage Docker images. You can override this with the CDK_DOCKER environment variable to use a drop-in replacement:

# Use Finch (AWS-supported Docker alternative)
export CDK_DOCKER=finch
npx cdk-agc

# Use Podman
export CDK_DOCKER=podman
npx cdk-agc

Note: Depending on your environment, you may also need to set the DOCKER_HOST environment variable to point to the container runtime's socket. For example:

• Finch (macOS): unix:///Applications/Finch/lima/data/finch/sock/finch.sock
• Podman: unix://$(podman machine inspect --format '{{.ConnectionInfo.PodmanSocket.Path}}')

Contributions are welcome! Please see CONTRIBUTING.md for details.

Apache-2.0 - see LICENSE for details.