Skip to content

DocumentDB

Amazon DocumentDB (MongoDB-compatible) clusters can accumulate waste through idle instances, missing Graviton migration opportunities, and suboptimal storage configurations.

Implementation Effort: Medium - Estimated time: 1-4 hours depending on the optimization type. Graviton migration requires instance modification; IO-Optimized requires cluster-level configuration change.

What We Detect

  • Idle instances -- DocumentDB instances with no active connections over an extended period
  • Graviton migration candidates -- Instances running on Intel/AMD instance families that could migrate to Graviton-based types for better price-performance
  • IO-Optimized storage -- Clusters that would benefit from switching to IO-Optimized storage configuration based on their I/O patterns

Why It Matters

DocumentDB instances are billed per hour regardless of usage. Graviton-based instances offer up to 30% better price-performance. IO-Optimized storage eliminates per-I/O charges, which can significantly reduce costs for I/O-heavy workloads.

Recommendations

  1. Idle instances -- Verify no application depends on the cluster, then delete
  2. Graviton migration -- Modify the instance type to the Graviton equivalent (e.g., db.r5 to db.r6g)
  3. IO-Optimized -- Switch the cluster storage type when I/O costs exceed 25% of total database spend

Keep on chasing 🧡