Opportunity Name:
RDS Rightsize Storage
AWS Resource Type:
RDS
Opportunity Description:
CloudFix identifies opportunities to reduce costs by resizing RDS storage volumes without impacting performance. It targets volumes where the allocated storage exceeds the required capacity, considering performance metrics and ensuring at least 20% free space remains. Recommendations include switching to GP3 where applicable, optimizing for cost without compromising on performance or availability.
Criteria for identifying the opportunity:
- Annual cost, extrapolated from the last 31 days of usage, exceeds the annual public cost threshold (default $100).
- Database storage types include GP2, GP3, and IO1.
- Ensures no performance degradation for GP2 due to IOPS reduction.
- Keeps at least 20% available space after resizing.
- Recommends enabling storage autoscaling where available.
Potential savings (range in % on annual basis):
- Expected to target up to a 30%-40% reduction on the bills by optimizing storage costs.
- Actual savings will depend on the current storage configuration and usage patterns.
Can CloudFix implement the fix automatically once I accept the recommendation?
No. Resizing RDS storage requires manual implementation. Below are the recommended approaches:
Implementation Methods:
1. Snapshot and Restore (Fastest approach)
- Take a snapshot of your current database
- Restore the snapshot to a new RDS instance with smaller storage
- Update your application to point to the new endpoint
- Delete the old instance after verification
- Best for: Development/test environments or when downtime is acceptable
2. Database Migration Service (DMS) (Recommended for production)
- Create a new RDS instance with desired smaller storage
- Set up DMS replication from the old instance to the new instance
- Switch applications to the new instance when replication completes
- Minimal downtime compared to snapshot method
- Best for: Production systems requiring minimal interruption
3. Manual Export/Import
- Export data using native database tools (mysqldump, pg_dump, etc.)
- Create a new smaller RDS instance
- Import the data
- Provides more control but requires more downtime
- Best for: Smaller databases or when data transformation is needed
Pre-Migration Checklist:
- Clean up before migration: delete old logs, temporary tables, unused indexes
- If you want to maintain the smaller size, disable storage autoscaling on the new instance
- Review IOPS implications—smaller volumes may have lower IOPS limits
Other considerations:
- Performance impact: The recommendation ensures there will be no performance degradation due to IOPS reduction or storage resizing.
- Data loss considerations: Recommendations include keeping at least 20% free space to accommodate data growth and avoid data loss risks.
- Security concerns: No direct impact on security settings. However, enabling storage autoscaling as recommended should be configured with security best practices in mind.
Priyanka Bhotika
Comments