Scaling down to 0 in aurora postgresql

Question

Hi,

We are using the command put-scheduled-action, to change the minimum capacity to 0 every day on specify hour.
He accept to change, but the scheduled don´t remove the read replica, the cluster stay with 1 read replica.
We try to change the state of the alarm that start the action, but on the history of the alarme it show that started the action, but the read replica was not removed.

The goal is to remove all read replica after the commercial hour when not using, but if is using, he scale up when necessarie and on morning we will use de put-scheduled-action to came back the minimum to 1.

There any way to make this work?

Best Regards,
tcanoas

Answer

Hi,

You can set the min and max to 0 as parameters to the put-scheduled-action command. But there is a catch since it also means that for that duration if you have any requirement for the replicas, it wont be auto available until next morning. Also note that Aurora Auto Scaling only removes Aurora Replicas that it created. When you want to start it again you set min to 1 and max to the desired upper limit.

Scaling lets you set a value of min 0 but it does not seem to drop to 0 if the max is anything other than 0. Logically it seems correct coz the scaling metrics are for replicas and whatever threshold values you set you would end up with min 1 unless min and max are both 0.

--Syd

Scaling down to 0 in aurora postgresql

相關內容