Amazon RDS pricing and cost optimization
Updated: 16 November 2026Request a quoteRDS cost optimization starts with the complete bill. Review schedules, sizing and storage against performance and recovery requirements.

For centrally managed protection, use the AWS Backup copy and restore cost checklist to connect database recovery requirements with vault inventory and the complete billing boundary.
Amazon RDS pricing: assemble a comparable estimate
There is no single Amazon RDS price that describes every database. The official pricing page directs you to engine-specific pricing and the AWS Pricing Calculator. Record the Region, engine, deployment, instance class and storage configuration with the date of the estimate. Use the applicable agreement for an invoiced customer rate rather than assuming a public list price is your contracted price.
| Estimate line | Configuration to capture | Review question |
|---|---|---|
| Database compute | Engine, class, topology and running hours | Does the selected rate describe the deployed configuration? |
| Storage and performance | Provisioned capacity, storage type and separately priced IOPS or throughput | Which dimensions apply to this engine and storage option? |
| Protection and movement | Backup storage, snapshot copies and transfer routes | Which charges occur outside the compute subtotal? |
| Additional features | Applicable Extended Support, Proxy and public IPv4 usage | Which additional services are present on the actual bill? |
The RDS for PostgreSQL pricing breakdown illustrates why storage, backup, data transfer and eligible Extended Support need separate lines. Review the corresponding pricing page for your engine. Do not carry a PostgreSQL example across to Oracle or SQL Server licensing, or substitute Aurora pricing for an RDS instance estimate.
- Save the dated estimate and exact configuration behind each rate.
- Reconcile observed usage before extrapolating a monthly budget.
- Identify discounts already covering the workload before adding a purchase.
- Separate credits, taxes and your commercial agreement from the technical comparison.
AWS also lists Database Savings Plans for eligible database usage, with a one-year spend commitment. Compare current eligibility and existing coverage with Reserved DB instances before choosing an instrument. Use the AWS commitment comparison for the purchasing boundary and the backup cost review for centrally managed protection. A lower compute rate should be evaluated against the complete database bill.
RDS cost optimization: choose the next database action
Rank changes by net effect on the complete database bill. Start with one database identifier, its owner and a representative billing period. The official RDS pricing guidance distinguishes engine and deployment choices, and describes additional Extended Support charges for eligible older MySQL and PostgreSQL versions. Include any applicable support line when assessing an engine upgrade.
| Review signal | Action to assess | Evidence before approval |
|---|---|---|
| Nonproduction database runs outside its useful hours | A supported stop and start schedule | Dependencies, residual charges and automatic restart behavior |
| Capacity appears larger than demand | A smaller eligible instance class | Peak memory, connections, latency and an application acceptance test |
| Storage or backup lines dominate | Review provisioned performance and retention | Measured I/O, growth needs and an approved recovery policy |
| Stable demand remains after approved changes | Compare an eligible reservation with current billing | Matching rules, existing coverage and planned engine or family changes |
For a stop schedule, apply the engine and deployment restrictions in the RDS documentation. Stopping eligible compute leaves charges for provisioned storage, applicable Provisioned IOPS, backups and, for a publicly accessible instance, public IPv4 addresses. The instance automatically restarts after seven days. Assign an owner to that restart and the next scheduled use.
Match the commitment to the remaining workload
RDS Reserved DB instances discount eligible instance usage; storage, backup and I/O remain separate. Matching depends on characteristics including Region, engine, instance class and licence terms. Size flexibility has engine restrictions. Check existing coverage against the proposed configuration before purchasing. Stopping or deleting a database does not cancel its reservation commitment. No Upfront and Partial Upfront reservations retain their hourly charges throughout the term, regardless of usage; an All Upfront payment is already committed. Check whether other eligible usage can consume the discount before counting a schedule change as a cash saving.
- Reconcile compute, storage, backup and applicable additional charges to the current bill.
- Ask the database owner to approve the service boundary and performance test.
- Apply one accepted change, then update the remaining demand and commitment model.
- Measure the result on a consistent cost basis and record any workload change.
Keep the database findings in the AWS cost optimization review. Use the commitment break-even calculator for a documented rate comparison and the realized savings register for follow-up. The EBS pricing breakdown concerns separately billed block volumes; reconcile service ownership before combining the totals.
AWS RDS cost: build a database-specific baseline
The official RDS pricing page separates pricing by database engine and deployment choices. Compute, storage, backup and transfer are distinct cost dimensions. Record the exact engine and configuration when reviewing an AWS cost RDS line: a rate from a different engine or availability configuration is not a comparable estimate.
| Area | Evidence | Decision |
|---|---|---|
| Database compute | Instance class and billed running time | Does measured demand justify the configuration? |
| Storage and I/O | Storage type, provisioned size and performance | What must remain provisioned? |
| Availability | Deployment topology and recovery requirement | Which failure scenario must the system withstand? |
| Backups | Retention policy and retained snapshots | Which data remains necessary? |
Reconcile the database with the AWS cost optimization audit before ranking findings. An application may also incur EC2 compute costs and network transfer charges. Preserve that full application boundary when estimating the effect of a database change.
Check idle databases without treating them as disposable
The RDS stopping documentation states that eligible stopped instances continue to incur provisioned storage, applicable Provisioned IOPS and backup charges, plus public IPv4 charges if the instance is publicly accessible. RDS automatically starts a stopped DB instance after seven days. Restrictions apply by engine and deployment. A shutdown proposal must account for those rules rather than assuming an instance stays stopped indefinitely.
- Ask the application owner whether the database serves a live dependency or a retained environment.
- Record maintenance, backups and the recovery procedure before changing schedules.
- Check whether the configuration supports stopping and what remains billed.
- Include the automatic restart behavior in the operating plan.
Unused compute does not imply unwanted data. A development database can be idle while its data remains needed for a test cycle. Separate the decision to stop compute from a decision to shorten retention or delete a snapshot. Each needs an owner and a documented acceptance condition.
Rightsize from performance evidence
For AWS RDS cost optimization, collect workload evidence over a representative cycle. Review memory pressure, connections, latency and query behavior alongside CPU. Ask the database team which bottleneck limits the application. A capacity reduction that increases query time or moves the bottleneck elsewhere can invalidate the original saving estimate.
- Identify the current cost and service baseline by database.
- Select one proposed configuration with documented performance assumptions.
- Test the application behavior and recovery procedure.
- Approve the change and its rollback condition before implementation.
Compare recurring cost after the change with the original period adjusted for workload growth. Separate a configuration effect from a traffic decline or a one-time credit. The realized savings measurement guide explains the register needed for that comparison. Keep storage and backup lines in the result even when the compute saving is the main reason for the mission.
A useful proposal names the engines and accounts included, the analysis period, the implementation responsibility and the evidence handed over. Ask for findings by database rather than a cloud-wide percentage. Make any commitment recommendation conditional on the demand that remains after approved sizing changes, and record dependencies on licence or contractual terms.

Questions before a cost review
What should I do first for RDS cost optimization?
Reconcile the full database bill to its engine, Region and availability configuration. Review useful running hours, performance evidence and storage requirements with the owner before estimating a new commitment.
Do RDS Reserved Instances discount storage and backups?
No. The RDS Reserved DB instance discount applies to eligible instance usage. Storage, backup and I/O charges remain separate, and the reservation must match the documented eligibility rules.
Can an RDS stop schedule eliminate the database bill?
No. Eligible stopped instances retain billable resources and automatically restart after seven days. Check engine and deployment restrictions, residual storage and backup charges, and any applicable public IPv4 charges before implementing a schedule.
Related workload decisions
Continue the review with aws lambda cost, ebs aws cost. Each guide addresses a separate decision within the same cloud cost boundary.