Databases of cluster doesn't stop about instance-scheduler-on-aws HOT 3 CLOSED

Hi @DevMasterSoonToBe

Have you tagged the RDS cluster itself or one of the instances in the cluster? For cluster scheduling Instance Scheduler needs to use the cluster APIs and so tags must be applied to the top-level cluster and not the underlying instances

from instance-scheduler-on-aws.

I have a primary and replica. They are both tagged with required tag for instance scheduler to work. I don't see an option to tag on the cluster level in the console. It is a mysql rds primary and replica setup. So its not actually a DB cluster, but instances(primary and replica)

from instance-scheduler-on-aws.

Ah gotcha, thanks.

This looks to be a service limitation of RDS itself as described here: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_StopInstance.html#USER_StopInstance.Limitations

You can't stop a DB instance that has a read replica, or that is a read replica.

So unfortunately there's no way for Instance Scheduler to stop the instance

from instance-scheduler-on-aws.