Skip to content

RDS convert magnetic to gp3

-1

Hi,

Having issues converting RDS with magnetic storage to SSD. The RDS instance is running and its Storage type is Magnetic.

We're sorry, your request to modify DB instance X has failed. You can't modify standard (magnetic) storage type: current: gp3, requested: standard.

CanNotUpdateToGP3

Your DB instances are using magnetic storage. Magnetic storage isn't recommended for most of the DB instances. Choose any of this storage type: General Purpose (SSD) or Provisioned IOPS.

RDS: scheduledChangearn:aws:health:ap-southeast-2::event/RDS/AWS_RDS_PLANNED_LIFECYCLE_EVENT/AWS_RDS_PLANNED_LIFECYCLE_EVENT_X Start time: Fri, 1 May 2026 07:00:00 GMT End time: undefinedLatest update: [AWS Health may periodically trigger reminder notifications about this communication if resources remain unresolved.]You are receiving this notification because you have one or more Amazon RDS databases on magnetic volumes. Amazon RDS will begin deprecating magnetic volumes starting May 1, 2026.

The instance was created via Opentofu (Terraform) from a snapshot which has "Storage type Magnetic". I tried deploying the RDS from the snapshot to gpX but it wouldn't allow it either.

Do I have to deploy a fresh RDS instance with gpX storage and import a .bak of the MS SQL Express database and re-snapshot to get around it? Or can existing magnetic instances be migrated to ssd? I wonder how AWS is going to force the update on May 1st?

Regards, Dan.

2 Answers
0

You can convert your RDS instance from magnetic storage to gp3, but you cannot do this directly through a simple storage type modification. The error message you're receiving indicates that AWS doesn't support direct conversion from magnetic (standard) storage to SSD storage types through the modify operation.

Here are your options to migrate from magnetic to gp3 storage:

Option 1: Create a new instance from snapshot with gp3 When restoring from a snapshot, you should be able to specify a different storage type (gp3) during the restore process. This is different from modifying an existing instance. During snapshot restore, you can modify storage type settings even though the original snapshot used magnetic storage.

Option 2: Fresh instance with database import As you mentioned, you can create a new RDS instance with gp3 storage and migrate your SQL Server Express database using a .bak file import. This would give you a clean start with the desired storage type.

For SQL Server specifically: If you're using RDS for SQL Server, you have additional flexibility. You can add new storage volumes with gp3 storage type to your instance. For example, you could add a new gp3 volume and then move your databases to that volume, though this doesn't eliminate the magnetic volume entirely.

Recommendation: The cleanest approach would be to restore your snapshot to a new RDS instance and specify gp3 as the storage type during the restore operation. This should allow you to change the storage type while preserving your data. Make sure to specify the storage type, allocated storage, and if needed, provisioned IOPS and throughput settings during the restore process.

Given the May 2026 deprecation timeline, AWS will likely provide migration tools or automated processes closer to that date, but it's best to migrate proactively using one of the above methods.
Sources
Modifying settings for General Purpose SSD (gp3) storage - Amazon Relational Database Service
Working with storage in RDS for SQL Server - Amazon Relational Database Service

answered 8 months ago

EXPERT

reviewed 8 months ago

-1

Hi,

There's a mention in this RDS doc - https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Storage.html#CHAP_Storage.Magnetic that

Magnetic storage (legacy, not recommended)
....
Doesn't allow you to convert to a different storage type when using the SQL Server database engine.

But given the AWS RDS team has contacted you about the scheduled change, I would suggest you contact AWS Support on the free support plan and inquire about RDS team's recommended option to proceed in SQL Server cases with magnetic volumes given their upcoming auto-migration plan as well.

Thanks.

AWS
EXPERT

answered 8 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.