Databases of cluster doesn't stop

[DevMasterSoonToBe]

Describe the bug

Databases clusters that have source and replica don't stop even though it should be controlled with instance scheduler.

To Reproduce

1. Create source and read replica rds
2. Tag with required tag in order for instance scheduler to work
3. Check Cloudwatch logs for an error

Expected behavior

Instance scheduler to stop instances that are source & read replica

Please complete the following information about the solution:

• [ ] Version: v1.5.3

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0030) instance-scheduler-on-aws v1.5.1". You can also find the version from releases

• [ ] Region: all regions have this issue
• [ ] Was the solution modified from the version published on this repository? No
• [ ] If the answer to the previous question was yes, are the changes available on GitHub?
• [ ] Have you checked your service quotas for the sevices this solution uses? Not related
• [ ] Were there any errors in the CloudWatch Logs? Yes. - Can not schedule rds instance "database-1" because it is the source for read copy instance(s) mydbinstance

Screenshots If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context Add any other context about the problem here.

[CrypticCabub]

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

[DevMasterSoonToBe]

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)

[CrypticCabub]

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