Abstract: In some implementations, a scheduling system for automated suspension and resumption of cloud resources is described. The scheduling system receives a scheduling tag defining custom uptime or downtime windows for a cloud resource over a scheduling period. A continuous schedule with recurring uptime and downtime windows is determined, and, at periodic scans, the scheduling system aligns the resource's current state with a target state based on this schedule. The scheduling system may support custom syntax for database cloud resources, global or resource-specific overrides to temporarily modify the schedule without changing the scheduling tag, and buffer periods before uptime windows to account for delays in resource start-up.

Abstract: In some implementations, a scheduling system may receive a scheduling tag to define a custom schedule that includes one or more downtime windows for a cloud resource over a scheduling period. The scheduling system may determine a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the one or more downtime windows defined in the scheduling tag. The scheduling system may determine at a current scan time, whether a target state for the cloud resource is a running state or a suspended state based on the one or more uptime windows and the one or more downtime windows included in the regular continuous schedule. The scheduling system may align a current state of the cloud resource with the target state.

Abstract: In some implementations, a scheduling system may receive a scheduling tag to define a custom schedule that includes one or more downtime windows for a cloud resource over a scheduling period. The scheduling system may determine a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the one or more downtime windows defined in the scheduling tag. The scheduling system may determine at a current scan time, whether a target state for the cloud resource is a running state or a suspended state based on the one or more uptime windows and the one or more downtime windows included in the regular continuous schedule. The scheduling system may align a current state of the cloud resource with the target state.

Abstract: In some implementations, a scheduling system may receive a scheduling tag to define a custom schedule that includes one or more downtime windows for a cloud resource over a scheduling period. The scheduling system may determine a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the one or more downtime windows defined in the scheduling tag. The scheduling system may determine at a current scan time, whether a target state for the cloud resource is a running state or a suspended state based on the one or more uptime windows and the one or more downtime windows included in the regular continuous schedule. The scheduling system may align a current state of the cloud resource with the target state.

Abstract: In some implementations, a scheduling system may receive a scheduling tag to define a custom schedule that includes one or more downtime windows for a cloud resource over a scheduling period. The scheduling system may determine a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the one or more downtime windows defined in the scheduling tag. The scheduling system may determine at a current scan time, whether a target state for the cloud resource is a running state or a suspended state based on the one or more uptime windows and the one or more downtime windows included in the regular continuous schedule. The scheduling system may align a current state of the cloud resource with the target state.