Configure additional storage volumes with Amazon RDS for SQL Server
Database Blog
This article explains how to configure additional storage volumes for Amazon RDS for SQL Server instances, enabling better storage organization and performance optimization.
- Attach up to three additional storage volumes to RDS SQL Server instances
- Additional volumes support gp3 and io2 storage types for performance optimization
- Volumes map to Windows drive letters: H:\, I:\, and J:\ drives
- Add volumes during instance creation or to existing instances via console or AWS CLI
- Scale existing volumes without downtime during low-activity periods
- Restore databases to specific additional storage volumes using SQL commands
- Delete unused volumes when not in use; default D:\ drive cannot be deleted
- Distribute data and log files across volumes for granular control
Additional storage volumes provide flexibility for organizing workloads, improving performance through dedicated IOPS, and scaling storage independently while maintaining high availability.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Apr 14
2026
2026
Improving storage with additional storage volumes in Amazon RDS for SQL Server
May 1
2026
2026
Amazon RDS for SQL Server supports read replica with additional storage volumes
Jan 13
2026
2026
Best practices for creating and reorganizing data with additional storage volumes in Amazon RDS for Oracle
Jun 18
2026
2026
Amazon RDS for SQL Server increases the maximum size and provisioned performance of General Purpose (gp3) volumes
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.