Amazon RDS · Finder + guided fix

RDS Retype Single Availability Zone

RetypeSingle Availability Zone

Transition non-critical RDS Multi-AZ deployments to Single-AZ to cut database costs by up to 50%. CloudFix identifies candidates where HA is not needed.

Guided fix
Effort: Advanced
Action: Retype
Amazon RDS

What happens, in order.

Finder · read-only
Finds the opportunity
Scans your connected accounts with a read-only role. It can see resource metadata and usage; it can’t change anything.
You
Review in Recommendations
It appears in your Recommendations view with what it would save.
Guided fix
You make the change
You apply it yourself, following the fix’s step-by-step instructions; the write-up below explains it.

Finder role

Read-only. It can see resource metadata and usage. It can’t change anything.

Fixer role

Not used here: this one is a guided fix, so the change is yours to make.

Saves by

This recommendation identifies Amazon RDS instances and clusters configured with Multi-AZ deployments that can be optimized for cost by transitioning to Single-AZ deployments. This is particularly useful for development, testing, non-production, or other non-critical environments where high availability is not a primary concern.

Optimize your Amazon RDS costs by identifying and transitioning non-critical Multi-AZ deployments to Single-AZ configurations. CloudFix’s RDS Retype Single Availability Zone Finder/Fixer helps you target RDS instances that don’t require high availability, potentially saving up to 50% on these database costs.

What Does This Finder/Fixer Do?

This Finder/Fixer identifies Amazon RDS instances and clusters configured with Multi-AZ deployments that can be optimized by converting to Single-AZ deployments. It focuses on non-critical environments where high availability might not be necessary, allowing you to significantly reduce costs without impacting appropriate workloads.

By analyzing usage patterns and costs, the Finder identifies candidates for conversion and estimates the potential savings. While this Finder provides recommendations, the actual conversion requires manual implementation since it impacts database availability characteristics.

Why Is This Important?

Multi-AZ deployments are an excellent feature for mission-critical production workloads, providing automatic failover and high availability. However, they come at a significant cost premium (typically double the cost of a Single-AZ deployment) because you’re essentially running two synchronized database instances.

Many organizations inadvertently provision Multi-AZ deployments for non-critical workloads for several reasons:

Configuration is copied from production to development/test environments
Default templates or IaC modules enable Multi-AZ by default
Over-provisioning during initial deployment without subsequent optimization
Legacy databases that have been repurposed but never reconfigured

This represents a significant cost-saving opportunity without affecting appropriate workloads, as many development, testing, and non-critical deployments don’t require the high availability that Multi-AZ provides.

How Does The Finder Work?

CloudFix uses your cost and usage data to find RDS instances and clusters running Multi-AZ deployments where the standby replica is adding meaningful cost, and estimates the annual savings from converting each one to Single-AZ. Finding is read-only.

These candidates appear in your Recommendations with their estimated savings. The decision to implement the change remains with you, allowing you to evaluate each case based on your specific requirements and risk tolerance.

What Happens When The Fixer Runs?

This recommendation requires manual implementation as it involves making a significant configuration change to your database infrastructure. CloudFix provides detailed information to help you make an informed decision, but does not automatically modify your RDS deployments.

To convert from Multi-AZ to Single-AZ, you would typically:

Evaluate: Confirm the database isn’t serving critical workloads requiring high availability.
Plan: Schedule the change during a maintenance window to minimize impact.
Implement: Use the AWS Management Console, CLI, or API to modify the instance.
Verify: Ensure the database functions properly after the conversion.

You can apply the change immediately or schedule it for your next maintenance window.

AWS Services Affected

Amazon RDS

Benefits

Significant Cost Reduction: Up to 50% savings on eligible RDS instances (PostgreSQL, MySQL, MariaDB, etc.) and up to 24% for SQL Server Enterprise Edition.
Resource Optimization: Aligns database deployment configuration with actual workload requirements.
Improved Cost-to-Value Ratio: Ensures you’re only paying for high availability where it’s needed.
Simplified Management: Reduces complexity for non-critical environments.
Enhanced Cost Visibility: Identifies under-optimized database deployments across your organization.

Potential Risks

Converting from Multi-AZ to Single-AZ involves several important considerations:

Reduced Availability: Single-AZ deployments don’t provide automatic failover capabilities, increasing risk of downtime during AWS maintenance or infrastructure failures.
Maintenance Impact: Database maintenance operations may cause longer downtime in Single-AZ deployments.
Disaster Recovery: Without a standby replica, recovery from instance failures will take longer and rely on point-in-time backups.
Application Expectations: Applications designed with high-availability assumptions may need reconfiguration.

Before implementing this change, evaluate your workload criticality, backup strategy, and acceptable recovery time objectives (RTO) to ensure alignment with business requirements.

Cost Savings

The cost savings from converting Multi-AZ to Single-AZ deployments are substantial:

For PostgreSQL, MySQL, Oracle, and MariaDB: Up to 50% savings on instance, storage, and IOPS costs.
For SQL Server Enterprise Edition: Up to 24% annual cost reduction.

These savings come primarily from eliminating the standby replica instance and its associated storage. For example, a db.m5.large Multi-AZ PostgreSQL instance in US East costs $0.342/hour, while the equivalent Single-AZ deployment costs $0.171/hour, a direct 50% saving.

With database costs often representing a significant portion of cloud spending, targeting non-critical Multi-AZ deployments can yield substantial overall savings, especially in larger environments with many database instances.

FAQ

How do I identify which RDS instances are appropriate to convert?

Focus on non-production workloads like development, testing, QA, and staging environments. Consider workloads where the availability requirements don’t justify the additional cost of Multi-AZ deployments. Always consult with application owners to verify availability requirements.

Will switching to Single-AZ cause downtime?

Converting from Multi-AZ to Single-AZ typically involves minimal disruption when applied immediately. Otherwise, the change occurs during the next maintenance window. Brief connectivity loss may occur during the transition.

How does this affect my backup strategy?

In Multi-AZ deployments, backups are taken from the standby instance to avoid performance impact on the primary. After converting to Single-AZ, backups will occur on the primary instance. Review and potentially adjust your backup windows to minimize impact on critical workloads.

Can I convert back to Multi-AZ later if needed?

Yes, you can convert back to Multi-AZ at any time using a similar process. The transition to Multi-AZ involves creating and synchronizing a standby instance, which can take time depending on the database size.

Ready to start saving on AWS? See how much you could cut from your cloud bill with a free cost optimization assessment, or explore CloudFix automated Finder/Fixers that eliminate waste across 30+ AWS services.

Browse all 110+ finders

See whether this one applies to your account.

A free savings assessment reports which fixers can be applied to your environment. Results typically within 24 hours.

Get a free savings assessment See how CloudFix works

What happens, in order.

Finds the opportunity

Review in Recommendations

You make the change