Practical guide
RDS MySQL pricing: calculate the instance-hour subtotal
estimate RDS MySQL Single-AZ instance cost. Includes a worked example, calculator scope, and practical questions.
Updated · Sources checked
Begin with the deployment the calculator actually models
An RDS instance estimate needs the engine, instance class, deployment type, region, and billable runtime. The StackCalcs tool covers MySQL Single-AZ db.t3 On-Demand instance charges in US East. Its result should not be treated as PostgreSQL, Multi-AZ, or a complete storage-inclusive database quote.
This narrow scope is useful for comparing supported instance sizes or the runtime of a development database. Keep all other configuration choices constant so the comparison answers one clear question.
Worked example: production and development runtime
Suppose one supported MySQL instance runs for a 730-hour planning month while a second development instance runs for 220 hours. If both use the same hourly rate R, combined instance cost is 950R.
Do not enter two instances at 730 hours unless both actually run for that duration. Instead, calculate the production and development scenarios separately and sum them. If the development class differs, its 220 hours must use that class’s own rate.
Now suppose the development database is needed for an additional 40 hours of testing. Its marginal compute cost is 40 times the matching hourly rate. This change does not automatically increase provisioned storage by the same percentage because storage and runtime are different quantities.
Add the omitted database components
Storage allocation, provisioned performance where applicable, backup beyond the applicable allowance, transfer, and other features need separate line items. Burstable CPU-credit charges can also matter for sustained load. A low instance-hour subtotal does not prove the database is correctly sized.
For short or interrupted usage, check the billing minimum and timing rules. The page’s monthly model accepts whole hours, while AWS billing has more detailed increments. Do not assume a stopped database will remain stopped indefinitely without checking the service behavior and your operational automation.
Frequently asked questions
Does Single-AZ estimate Multi-AZ by changing the count to two? That is not a reliable substitute for deployment-specific pricing. Use the actual Multi-AZ configuration and rates.
Does this include database storage? No. Keep the instance-only result separate and add storage and other applicable components before using it as a budget.
Calculate your scenario
Use the rds cost calculator. Keep the displayed region, pricing date, billing units, and exclusions alongside your result. The arithmetic examples above illustrate usage or explicitly hypothetical rates; they are not AWS quotes.
Source
Billing structure checked against official AWS documentation on September 6, 2026.