Skip to content
Pinter Computing

Knowledge Base for IT Professionals, Teachers, and Astronauts

Pinter Computing

Knowledge Base for IT Professionals, Teachers, and Astronauts

  • Home
  • Programming
  • DevOps
  • Project Management
  • Software and Hardware
  • Miscellaneous
  • Egyebek
  • About
  • Experience
  • Education
  • Contact
  • Home
  • Programming
  • DevOps
  • Project Management
  • Software and Hardware
  • Miscellaneous
  • Egyebek
  • About
  • Experience
  • Education
  • Contact
Close

Search

Home/Knowledge Base/Cannot modify the instance class because there are no instances of the requested class available in the current instance’s availability zone
Knowledge Base

Cannot modify the instance class because there are no instances of the requested class available in the current instance’s availability zone

By Laszlo Pinter
September 13, 2021 1 Min Read
0

When you change the instance type of an AWS RDS instance, the availability zone of the instance has to have available capacity of the selected type.

Some older availability zones (us-east-1a) have more old instance types than new types available. If the instance type you selected is not available in the current zone of the instance you get the error message:

We’re sorry, your request to modify DB instance … has failed.

Cannot modify the instance class because there are no instances of the requested class available in the current instance’s availability zone. Please try your request again at a later time.

To upgrade an RDS instance to a new type that is not available in the current availability zone:

  1. Find an AZ that has the desired instance type
    • Try to launch an instance with the new instance type and see which zones have available capacity
  2. Change the RDS instance to multi-AZ
    • Click the Modify button and change the instance to multi-AZ
  3. If the secondary instance is not created in a zone that has available capacity of your desired instance type, change the instance back to single-AZ and return to step 2, to set it to multi-AZ again.
  4. Reboot with failover to the secondary instance to make it the primary instance in the new availability zone
    • Click the Actions button and select Reboot
    • Select Reboot with failover
  5. Change the instance back to single-AZ
  6. Upgrade the instance type

Tags:

AWSDevOpsRDS
Author

Laszlo Pinter

Follow Me
Other Articles
Previous

Exit from Bash script on error without closing the terminal window

Next

Move AWS EC2 instance to another subnet or availability zone

No Comment! Be the first one.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Search

Last Changes

  • DevOps Engineering part 1. (Mac) - Make your Macintosh easier to use June 25, 2026
  • Japan travel tips June 22, 2026
  • How to stop the rain and snow in Cities: Skylines II June 20, 2026
  • Cities: Skylines II Developer Mode June 20, 2026
  • 'CSII_MANAGEDPATH' has incorrect path(s) when building Cities: Skylines II mod June 20, 2026

Tags

.NET .NETcore 3Dprinting ASP.NET Core AutodeskInventor AWS C# Chef cloud DevOps Docker EntityFramework Games Git Go iOS iPad iPhone iPod Java Kubernetes Linux MacOSX MSSQL MVC Node.js Packer PowerShell Python RDS RightScale Ruby security Splunk TeamCity Terraform TestKitchen Tomcat Ubuntu Vagrant VirtualBox VisualStudio Windows WordPress Xcode

Recent Comments

  • Zengei László on MyHeritage családfa exportálása és küldése emailben
  • Raúl Castillo on DynDns update error
  • MICHAEL on Windows Media Player 12 cannot find the album information
  • Nargis on Configure Epson ET-3850 scanning on Windows 11
  • Venczelné Zemen Erika on Delta S2302 termosztát programozása

–

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org
Copyright 2026 — Pinter Computing. All rights reserved.