What's new?

• Setting DB instance and DB cluster schedules is now easier: the AWS > RDS > DB Instance > Schedule and AWS > RDS > DB Cluster > Schedule policies manage both fixed schedule windows and tag-based schedules from a single policy. Each schedule window is now available with Tag override, which enforces the window while letting individual DB instances or clusters override it with a schedule of their own via their schedule tag, and the new Enforce: Per Schedule > Tag schedule option enforces only the schedule from the tag. The tag key is configurable via the Schedule > Tag policy (formerly Schedule Tag > Name, default turbot_custom_schedule).
• With scheduling consolidated into the Schedule policies, the separate AWS > RDS > DB Instance > Schedule Tag and AWS > RDS > DB Cluster > Schedule Tag policies have been deprecated and now live under their respective Schedule policies in the policy hierarchy. Use the with Tag override or Enforce: Per Schedule > Tag schedule options instead - they provide the same functionality from a single policy. Existing Schedule Tag settings continue to be honored.
• The Schedule controls now wait one hour after starting or stopping a DB instance or cluster before acting again, so a manual action taken in the meantime is not immediately overridden.

Bug fixes

• Fixed the AWS > RDS > DB Instance > Schedule and AWS > RDS > DB Cluster > Schedule controls remaining stuck in a TBD state with the reason Precheck policy not fully installed or has incorrect target.

Policy Types

Renamed

• AWS > RDS > DB Cluster > Schedule Tag to AWS > RDS > DB Cluster > Schedule > Schedule Tag [Deprecated]
• AWS > RDS > DB Cluster > Schedule Tag > Name to AWS > RDS > DB Cluster > Schedule > Tag
• AWS > RDS > DB Instance > Schedule Tag to AWS > RDS > DB Instance > Schedule > Schedule Tag [Deprecated]
• AWS > RDS > DB Instance > Schedule Tag > Name to AWS > RDS > DB Instance > Schedule > Tag