Back
Database Management

Reliable database management for modern, high-performance systems.

Back
Data Modernisation

Reliable database management for modern, high-performance systems.

Back
Data Engineering

Reliable database management for modern, high-performance systems.

Back
Analytics & Intelligence

Reliable database management for modern, high-performance systems.

Back
Data Strategy Consulting

Reliable database management for modern, high-performance systems.

RDS Capacity Reservations for Database Migration Cutovers

Jawahar Viswanathan
Published on
November 22, 2026

A migration cutover is a bad time to find out that the Availability Zone you planned for has no spare capacity. RDS capacity reservations hold DB instance capacity for a specific engine, instance class and Availability Zone, so the capacity is there when you need it. In this walkthrough, we set one up for an RDS MySQL test database, attached a database to it, and cancelled it after the cutover. Every screenshot comes from our own lab account in us-east-1, using MySQL on db.t3.micro.

Capacity reservations reduce one specific risk: running out of capacity in the zone you planned to use. They do not lower your bill, and they do not guarantee a failover on their own. The limits section below covers what they can and cannot do.

At a glance: capacity reservations vs reserved instances

In the Aurora and RDS console, Capacity reservations has its own page in the left menu, separate from Reserved instances. The two solve different problems.

FeatureCapacity reservationsReserved DB instances
What you getHeld capacity in a specific Availability ZoneA billing discount
CommitmentNone for immediately active reservationsFixed one-year or three-year term
Billing discountNone, but you can combine it with reserved instances or Database Savings PlansYes
Instance limitsYour On-Demand DB instance quotaVaries by Region

Capacity reservations hold capacity. Reserved DB instances give a billing discount.

Cutover path in the console
  1. Create reservationMySQL, db.t3.micro, us-east-1a, 1 instanceActive
  2. Create database from itOnly the matching engine can be chosenForm tied to reservation
  3. Database placed in the slotSame engine, class and zone as the reservationConnected
  4. Reservation in useShows 0 of 1 capacity availableIn use
  5. Cancel after cutoverRunning database continues as On-DemandCancelled
  6. Clean up the labTest database deletedLab only

Cancelling stops the charge for the held capacity. It does not stop a database that is already running.

The six steps from creating a reservation to cancelling it after a cutover

Before you start

Four settings decide whether a database can use a reservation: the engine, the DB instance class, the license model (for engines that offer more than one), and the Availability Zone. They must match exactly. Plan them before you create the reservation, because the console restricts editing while the reservation is in use. MySQL is one of the engines covered on our MySQL database page, so the steps below use it throughout.

Check your On-Demand DB instance quota as well. Reserved capacity counts once for every Availability Zone you reserve in. One instance reserved across two zones uses two units of quota.

Creating a capacity reservation

Create capacity reservationAurora and RDS console
EngineMySQL
DB instance classdb.t3.micro
Availability Zoneus-east-1a
Reserved capacity per AZ1
Capacity reservation startsImmediately
Estimated cost$0.41 per day
Create capacity reservation
Successfully created capacity reservation
StatusPendingActive

Creating the reservation: the price estimate appears, the reservation is created and turns Active

Step 1: Open the Capacity reservations page

In the Aurora and RDS console, choose Capacity reservations in the left menu. Our account had none, so the page showed an empty list and a Create capacity reservation button.

Aurora and RDS console showing the empty Capacity reservations page, with a Create capacity reservation button
Capacity reservations page before any reservation exists

Step 2: Choose the engine and instance class

Pick the engine (MySQL in our test) and the DB instance class (db.t3.micro). A warning on the page says that editing is restricted while the reservation is in use, so get these right the first time.

Step 3: Name it, pick the Availability Zone and set the quantity

We named the reservation capacity-reservation-2, chose us-east-1a, and reserved one instance in that zone.

Step 4: Set the start and end times

A reservation can start immediately or at a set time. It can also end at a set time, so billing stops on its own. The console estimated the cost at $0.41 per day for this configuration.

Capacity reservation start and end settings, with an estimated cost of $0.41 per day
Start and end settings, with the price estimate

Step 5: Confirm the reservation is active

The reservation became active straight away. It appears in the list with its name and a dbcr- ID. A new database attaches to that ID.

Attaching a database to the reservation

Create database from reservationReservation
EngineMySQL
DB instance classdb.t3.micro
Availability Zoneus-east-1a
database-1 statusCreatingConfiguring enhanced monitoring
Reservation in use
Capacity available0 of 1
Connected databasesdatabase-1

The database lands in the reserved slot, and the reservation shows it as connected

Step 6: Create the database from the reservation

Choose Create database from the reservation. The form is tied to that reservation, and only the matching engine, MySQL, is available to select.

Step 7: Check the reservation in the database settings

The capacity reservation carries into the new database's configuration, alongside the usual settings.

Database Insights monitoring choice and the Create database button in the RDS console
The capacity reservation carried into the database settings

Step 8: Confirm the database landed in the reserved slot

database-1 was created in us-east-1a on db.t3.micro, which matches the reservation exactly.

Step 9: Check the reservation in use

The reservation now shows 0 of 1 capacity available, with database-1 listed under Connected databases. The database runs on the reserved capacity.

Cancelling after the cutover

Capacity reservationsAurora and RDS console
Successfully cancelled capacity reservation
ActiveCancelled
No reservations to display
Deleting 1 instancedatabase-1Deleting

Cancelling after the cutover: the status changes to Cancelled, the list empties, and the test database is deleted

Step 10: Cancel the reservation

After the cutover, cancel the reservation so you stop paying to hold capacity. Its status changes to Cancelled. Cancelling does not stop a running database. Any DB instance still running in the reservation continues as a normal On-Demand instance.

Step 11: Confirm nothing is left reserved

With cancelled reservations hidden, the list was empty again.

Step 12: Clean up the lab

We deleted the test database. In a real migration, the database would keep running at normal On-Demand rates after you cancel the reservation.

Gotchas that cost time

  • A mismatch fails the call. If the engine, class, license model or Availability Zone differs from the reservation, the create or modify request fails with an error saying that zone does not have enough capacity. Check for a mismatch first, then for a real capacity shortage.
  • A modify request needs a class change. To move an existing instance into a reservation, the same request must also change the instance class, the Multi-AZ setting or the license model. A request that only names the reservation fails.
  • Multi-AZ needs two zones. To place a Multi-AZ instance, reserve in at least two Availability Zones, so that both the primary and the standby have capacity. Our high availability and disaster recovery team can review that layout with you.
  • Reserve in every zone you may need. A database in a zone you did not reserve cannot use the reservation, even in the same Region.

Limits to know

LimitWhat it meansWhat to do instead
Blue/Green deployments are not supportedThe green environment does not draw from a reservationPlan the target capacity separately, and test the switchover without relying on a reservation
Aurora Serverless v2 (db.serverless) is not supportedServerless v2 instances cannot use a reservationReserve a provisioned instance class instead
RDS Custom engines are not supportedcustom-oracle-* and custom-sqlserver-* engines cannot use reservationsUse a standard RDS engine for reserved capacity
One Region, selected zones onlyA reservation does not cover another Region, so it does not cover cross-Region DRCreate a reservation in each Region and zone you need
Compute onlyReservations do not hold storage or I/OPlan storage and IOPS separately
Future-dated bookingsBook 5 to 120 days ahead, with a commitment of at least 14 days (12 weeks for the X family)Pick the cutover date early and confirm it fits the commitment
Future-dated instance rulesOnly C, M, R, T and X classes. M and R must be generation 7 or later. At least 32 vCPUs per zoneCheck the instance class before you book
Commitment and schedulingA scheduled reservation cannot be cancelled. An active future-dated reservation cannot be cancelled until its commitment endsSet the start date and duration with care

Limits to check before you book a reservation for a cutover

Where it fits in a DBA's day

A capacity reservation belongs in the migration runbook. Add it before the cutover window, check its state the day before, and put the cancel step in the post-cutover checklist. A future-dated reservation can hold capacity for a fixed cutover date, but remember the commitment. Watch the cost estimate too: a reservation you forget to cancel keeps billing even when no database uses it. For the wider move, our cloud database migration and database migration services teams can plan the full runbook, and our DBA managed services cover the work after the cutover. For more on AWS work, see our AWS partner page.

Wrapping up

Capacity reservations are simple to set up, and they remove one risk from a cutover: finding no capacity in the zone you planned for. Test the steps in a lab first, and check the limits against your own engine and instance class. If you are planning a migration, talk to us through our contact page, or start with a free database audit to see where your databases stand.

Frequently Asked Questions

1. Am I charged when no database uses a reservation?

Yes. Billing starts when an active reservation is created and continues until you cancel it or it expires. Cancel it right after the cutover, or set an end time when you create it.

2. Can I use a reservation for an engine other than MySQL?

Yes, but each reservation is tied to one engine. Create a separate reservation for each engine and instance class you need.

3. Does a reservation protect a Multi-AZ failover?

It helps, but only if you reserve capacity in both the primary and the standby zones. A Multi-AZ instance needs capacity in both.

4. Can I use a reservation for cross-Region disaster recovery?

No. A reservation applies to one Region and the zones you choose in it. For DR in another Region, create a reservation there.

5. What happens to a running database when I cancel its reservation?

It keeps running as a normal On-Demand instance. You stop paying for the held capacity, not for the database.

6. Does a reservation hold storage?

No. It holds compute capacity for the instance class only, not storage or I/O.

Related reading

Sources: AWS, Amazon RDS User Guide and Aurora User Guide, On-Demand Capacity Reservations (docs.aws.amazon.com/AmazonRDS/latest/UserGuide/capacity-reservations.getting-started.html).

Jawahar Viswanathan

Jawahar Viswanathan has 5 years of experience in database administration, specializing in MySQL, AWS, and database performance management. His expertise includes database optimization, high availability, migrations, and maintaining reliable database environments for enterprise workloads.

Our Latest Blogs

From monitoring to modernization, GeoPITS provides expert database management services that enhance performance, strengthen security, and reduce operational costs.

Ready to Transform Your Data?

Geopits works alongside your team as a strategic partner, starting with stabilizing your current databases, then modernizing your data infrastructure, and ultimately helping you unlock the full potential of AI.

170

Happy Clients so far

2100+

Databases Managed

142+

Successful Migrations

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.