Satya walks you through troubleshooting
storage-full errors in RDS


My Amazon Relational Database Service (Amazon RDS) DB instance is out of storage, and I can't stop, restart, or connect to the instance.

To avoid the STORAGE_FULL state, consider using one or more of the following preventative measures:

An Amazon RDS DB instance in the STORAGE_FULL state won't have enough available space to perform basic operations, such as connecting to or restarting the instance. To resolve this issue, follow these steps:

Note: If your Amazon RDS DB instance is not in the STORAGE_FULL state, see Cannot Connect to Amazon RDS DB Instance for additional troubleshooting steps.

  1. Confirm that the DB instance status is STORAGE_FULL.
  2. Add more storage space to the instance. For more information, see Amazon RDS DB Instance Running Out of Storage.
  3. Increase the Allocated Storage property of your DB instance to free up additional space. For more information, see Modifying an Amazon RDS DB Instance and Using the Apply Immediately Parameter.
    Note: In most cases, a small increase to the Allocated Storage allows you to reconnect to the instance so that you can perform additional troubleshooting.

Amazon RDS for SQL Server

There are some limitations for modifying the storage of some DB instances. In the console, the Allocated Storage option is disabled if your DB instance isn’t eligible. If you want to scale storage Amazon RDS for SQL Server instances but the option to modify the storage size is not available, you can migrate your data by using native backup and restore or by using a data migration tool to migrate to a new instance that has a Provisioned IOPS or General Purpose (SSD) storage type. For more information, see Modifying a DB Instance Running the Microsoft SQL Server Database Engine.

You can check eligibility by using the following AWS Command Line Interface (AWS CLI) command to return the valid storage options for your DB instance:


You can reduce space used in Amazon RDS SQL Server instances by performing these actions:

  • If your Amazon RDS instance has a storage full condition or you want to control the size of your DB logs, run the DBCC SQLPERF(LOGSPACE) TSQL query to review the size of the SQL Server Transaction Log and the percentage of log space used. If the percentage of log space used is low, but the transaction log file size is high, shrink the transaction log file to recover disk space. For more information, see Connecting to a DB Instance Running the Microsoft SQL Server Database Engine.
  • If the tempdb is using a large amount of available storage, shrink the tempdb database. Because the SQL Server tempdb grows automatically when auto-growth is enabled and there is no limit specified in maxsize, the tempdb consumes available storage.

Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center.

Published: 2015-10-13

Updated: 2018-09-24