Hi there!

From the notes, I understand that you are using Amazon Aurora MySQL-Compatible Serverless and sometimes encounter unexpected traffic. Please note that although the “Force the capacity change” option isn't selected by default, you can select it to scale without a scaling point. You might get errors, since your transaction will be interrupted, but can resubmit the transactions as soon as your Aurora Serverless v1 DB cluster is available. Which is only recommended if your application can recover from dropped connections or incomplete transactions. However, if that is not possible, you can modify the timeout action and other capacity settings at any time. Please refer to outlined AWS documentation [1] on modifying capacity on Aurora Serverless v1 DB cluster.

However, if you require instant scaling for demanding workloads you may consider upgrading to Aurora Serverless v2. Aurora Serverless v2 helps to automate the processes of monitoring the workload and adjusting the capacity for your databases. Capacity is adjusted automatically based on application demand. Please refer to outlined AWS documentation [2] & [3].

I hope you find the above information helpful.

Have a great day ahead!

References:

[1] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless.modifying.html [2] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.html [3] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.upgrade.html