How do I resolve issues that occur when Amazon RDS DB instances run out of storage?

3 minute read
0

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

Resolution

Note: If you can't connect to your Amazon RDS DB instance and the instance isn't in the storage-full state, then see Can't connect to Amazon RDS DB instance.

An Amazon RDS DB instance that's in the storage-full state doesn't have enough available space to perform basic operations. For example, you can't connect to or restart the instance. The instance accepts only allocated storage modifications. Modifications for other values are rejected.

Resolve the storage-full state

To resolve this issue, complete the following steps:

  1. Check the DB instance status to confirm that the status is storage-full.
  2. Increase the allocated storage of your DB instance by at least 10%.

When the DB instance is in the modifying state, the instance is operational. However, you can't make other storage modifications for 6 hours or until the status changes to storage-optimization.

In most cases, a small increase to Allocated storage allows you to reconnect to the instance so that you can perform additional troubleshooting.

For more information about how to troubleshoot storage issues on RDS DB instances, see the following resources:

Prevent storage-full state

To avoid the storage-full state, take the following actions:

Related information

Monitoring Amazon RDS log files

Amazon RDS now has a progress indicator for the storage optimization process

Monitoring Amazon RDS metrics with Amazon CloudWatch

2 Comments

What can be done to PostgreSQL to reduce the log files

replied 8 months ago

I managed an issuewith storage full when I couldn't increase storage space despite everything being fine, it still throw error it couldn't increase storage space. What I did: I enabled 2FA for my account and created access tokens for the cli. Using AWS cli, I increased storage. It threw the same error, but in the web console it has upgraded my db storage space and I could operate it

replied 3 months ago