If you encounter the "resize-not-allowed" error when attempting to downsize your Aura instance, it is likely a result of our recent change. We have implemented a change that enables customers to downsize their instances one level at a time. This alteration aims to prevent several issues:

1. Cluster Unavailability: Avoid occurrences where the Aura instance becomes unavailable due to the downsizing process.

2. Out of memory (OOM) leading to Resize Stagnation: Reducing the risk of the database encountering OOM issues, which could cause the resize process to remain stuck for an extended period.

As a result, you can only downsize Aura instances one size at a moment. For example, if you have a 16GB Aura instance and want to downsize it to 4GB, you need to first downsize the instance to an 8GB one and then perform another downsize from 8GB to 4GB.

It's important to note that we haven't imposed such limitations on upsizing. Upsizing a few sizes won't pose a capacity issue since it involves increasing resources rather than reducing them.
We appreciate your understanding as these measures are implemented to enhance the overall stability and performance of your Aura instance.

See also

• Unable to resize Aura instance
• Resize your Neo4j AuraDB Instance