Identify any Amazon RDS database instances that appear to run low on disk space and scale them up to alleviate any problems triggered by insufficient disk space and improve their I/O performance. The default threshold value set for the amount of free storage space is 10% as any value below this could have a serious impact on your database stability and performance. For example, if the free storage space becomes dangerously low, basic operations like connecting to the database will not be possible anymore.
The AWS CloudWatch metric utilized to detect RDS instances with low free storage space is:
FreeStorageSpace - the amount of available storage space. (Units: Bytes).
This rule can help you work with the AWS Well-Architected Framework
This rule resolution is part of the Cloud Conformity Security & Compliance tool for AWS
Low disk space will often lead to instability and slowdowns. Detecting RDS database instances that run low on disk space is crucial when these instances are used in production by latency sensitive applications as this can help you take immediate actions and expand the storage space in order to maintain an optimal response time.
Note 1: You can change the default threshold value (10%) for this rule on Cloud Conformity console and set your own value for the amount of available storage space to configure the storage limits for your RDS instances.
Note 2: Scaling up the storage space is applicable only to the following RDS instance types: MySQL, MariaDB, PostgreSQL and Oracle DB.
To identify any existing RDS instances that run low on disk space, available in your AWS account, perform the following:
To scale up (expand) the storage space for any RDS database instances that run low on disk space, perform the following actions:Note: During the scaling process, the RDS database instance is available for use (no downtime), but its performance may be degraded.