Upgrading from t2 to t3 instances in Amazon RDS can deliver up to 30% better CPU performance at the same price point, presenting a compelling opportunity for cost optimization and improved database performance.
Why This Policy Matters
Performance and Cost Benefits
Improved CPU Performance: t3 instances offer substantial performance improvements over t2
Cost Optimization: Same price point with better hardware capabilities
Modern Infrastructure: Leveraging latest generation hardware
Key Performance Improvements
Up to 30% higher CPU performance
More efficient processor architecture
Enhanced virtualization capabilities
Better burst performance characteristics
Implementation Guide
Identifying Existing t2 Instances
To identify t2 instances in your RDS environment:
Review AWS Management Console
Check Terraform or CloudFormation configurations
Use AWS CLI to list existing RDS instances
Infrastructure-as-Code Example (Terraform)
Before:
resource "aws_db_instance" "example" {
instance_class = "db.t2.medium"
# Other configuration parameters
}
After:
resource "aws_db_instance" "example" {
instance_class = "db.t3.medium"
# Other configuration parameters
}
Manual Migration Steps
Create snapshot of existing t2 instance
Restore snapshot to new t3 instance
Verify application compatibility
Switch traffic to new instance
Decommission old t2 instance
Infracost Integration
Infracost can help you:
Automatically detect t2 instances
Estimate potential cost savings
Preview migration costs before implementation
Include this policy in automated checks during infrastructure review
Cost Savings Potential
Estimated Savings Scenario
Example: Medium-sized database
Current: db.t2.medium ($X/month)
Upgraded: db.t3.medium (Same cost, 30% performance boost)
Annual Savings: Performance efficiency without additional cost
Calculation Factors
Instance size
Workload characteristics
Burst credit utilization
Application performance requirements
Considerations and Caveats
Potential Limitations
Verify application compatibility
Test performance before full migration
Some legacy applications might require additional tuning
Compatibility Checks
Review application performance metrics
Test database performance under load
Validate connection string and driver compatibility
Real-World Examples
Scenario 1: Web Application Database
A mid-sized e-commerce platform migrated from t2.medium to t3.medium:
Reduced latency by 25%
Maintained same monthly infrastructure cost
Improved overall user experience
Scenario 2: Analytics Database
A data analytics company transitioned RDS instances:
Achieved better query performance
Reduced CPU wait times
No additional infrastructure expenses
Best Practices
Gradually migrate instances
Use AWS Database Migration Service
Perform thorough testing
Monitor performance post-migration
Frequently Asked Questions (FAQs)
How difficult is the migration process?
Generally straightforward. Requires creating a snapshot and restoring to a new instance.
Will my existing configurations transfer?
Most configurations transfer directly. Minor parameter adjustments might be needed.
What if my application doesn’t support immediate migration?
Perform staged migration, test thoroughly, and update application components as needed.
Are there any hidden costs?
No additional costs beyond standard RDS pricing. Performance improvement is included.
How long does a typical migration take?
1-2 hours for most database instances, depending on size and complexity.
Create Free Account
This policy is supported in Infracost and available in the free trial. Sign up today and scan your code using our entire library of FinOps policies.