RDS Retype IO Optimized

Opportunity Name:

RDS Retype IO Optimized

 

AWS Resource Type:

RDS Aurora

 

Opportunity Description:

This opportunity targets Amazon RDS Aurora clusters that are not currently utilizing the I/O-Optimized storage type. With the launch of Aurora I/O-Optimized instances and storage, AWS has provided a solution designed for I/O-intensive applications. CloudFix can identify and recommend switching to Aurora I/O-Optimized storage, aiming for significant cost reductions while maintaining or enhancing performance for I/O-intensive workloads.

 

Criteria for identifying the opportunity:

• Analyze average instance, storage, and I/O costs over the past 90 days to calculate potential savings.
• Recommend switching the cluster's storage type to Aurora I/O-Optimized when modeled annual savings (current instance, storage, and I/O cost versus I/O-Optimized cost at a 30% instance and 125% storage premium, with I/O costs eliminated) are at least $100.
• Every instance in the cluster must be in a supported family (t3, t4g, r5, r6i, r6g, x2g, r7g, or Aurora Serverless v2) and the engine version must support I/O-Optimized (Aurora MySQL 3.03.1+; Aurora PostgreSQL 13.10+, 14.7+, or 15.2+).
• Annual cost, extrapolated from the last 90 days of usage, exceeds the annual public cost threshold (default $100).

 

Potential savings (range in % on annual basis):

• Targeting up to a 30%-40% reduction on the bills for I/O-intensive applications.
• Savings calculations factor in the increased costs of I/O-optimized instances and storage against the elimination of IOPs costs.
• Actual savings will depend on the specific usage patterns and configurations of the customer's Aurora instances.

 

Can CloudFix implement the fix automatically once I accept the recommendation?

No

 

Other considerations:

• Performance impact: Upgrading to I/O-Optimized instances may enhance performance for I/O-intensive applications, but it's important to assess the workload compatibility.
• Data loss considerations: Ensure that all data is backed up before making any changes to the storage type or instance generation to prevent any potential data loss.
• Security concerns: Verify that the new instance types and storage configurations do not alter any existing security postures or compliance requirements.
• Version compatibility: Ensure that the Aurora MySQL (3.03.1+) or PostgreSQL (13.10+, 14.7+, or 15.2+) version and instance family (t3, t4g, r5, r6i, r6g, x2g, r7g, or Aurora Serverless v2) are compatible with I/O-Optimized storage.

 

Additional Resources:

• Amazon Aurora
• Managing I/O for Amazon Aurora