Skip to content
Jump to bottom

add user facing doc for power scheduler #425

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
+139 −0
Open

add user facing doc for power scheduler #425

Changes from 3 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
2bbbebf
add user facing doc for power scheduler
morga471 Jun 15, 2026
5afcaec
expand links
morga471 Jun 15, 2026
a78abde
additional details and resources section
morga471 Jun 16, 2026
d2e0557
add blurb about DST
morga471 Jun 16, 2026
2ab9d7f
add new schedule for ditd windows patching
morga471 Jul 10, 2026
8936cbf
update doc, add new schedule, break out custom schedules
morga471 Jul 10, 2026
1cbcc12
sort
morga471 Jul 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
32 changes: 20 additions & 12 deletions aws/documentation/power-scheduler/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,17 +77,25 @@ All times below are `US/Eastern`.

| Schedule Value | Start | Stop | Days | Behavior |
|----------------|-------|------|------|----------|
| `weekday-9a-5p` | 09:00 | 16:59 | mon-fri | 9am to 5pm on weekdays |
| `weekday-7a-7p` | 07:00 | 18:59 | mon-fri | 7am to 7pm on weekdays |
| `weekday-6a-7p` | 06:00 | 18:59 | mon-fri | 6am to 7pm on weekdays |
| `weekday-8a-1p` | 08:00 | 12:59 | mon-fri | 8am to 1pm on weekdays |
| `ditd-rds-530a-930p` | 05:30 | 21:30 (Mon-Thu), 23:59 (Fri) | mon-fri | DITD preferred RDS window |
| `always-off` | n/a | n/a | n/a | Override: keep stopped |
| `always-on` | n/a | n/a | n/a | Override: keep running |
| `everyday-6a-9p` | 06:00 | 21:00 | mon-sun | 15-hour daily window |
| `weekday-6a-9p` | 06:00 | 21:00 | mon-fri | 15-hour weekday window |
| `everyday-9a-5p` | 09:00 | 17:00 | mon-sun | 9am to 5pm every day |
| `weekday-6a-12a` | 06:00 | 23:59 | mon-fri | 18-hour weekday window |
| `always-on` | n/a | n/a | n/a | Override: keep running |
| `always-off` | n/a | n/a | n/a | Override: keep stopped |
| `weekday-6a-7p` | 06:00 | 18:59 | mon-fri | 6am to 7pm on weekdays |
| `weekday-6a-9p` | 06:00 | 21:00 | mon-fri | 15-hour weekday window |
| `weekday-7a-7p` | 07:00 | 18:59 | mon-fri | 7am to 7pm on weekdays |
| `weekday-8a-1p` | 08:00 | 12:59 | mon-fri | 8am to 1pm on weekdays |
| `weekday-9a-5p` | 09:00 | 16:59 | mon-fri | 9am to 5pm on weekdays |

## Custom Schedules

All times below are `US/Eastern`.

| Schedule Value | Start | Stop | Days | Behavior |
|----------------|-------|------|------|----------|
| `ditd-rds-530a-930p` | 05:30 | 21:30 (Mon-Thu), 23:59 (Fri) | mon-fri | DITD preferred RDS window |
| `ditd-win-patch-7a-7p` | 07:00 (23:30 mon after second tues) | 18:59 | mon-fri | weekday 7a-7p + Start at 23:30 on first monday after seecond tuesday for patching |
Comment on lines +97 to +98
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Schedules may be used by any resource. I don't believe we need rds or win-patch in there.

I really do not want hundreds of custom schedules. Why can't weekday-7a-7p work for the ditd-win-patch?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where's their justification for this (and expected duration)? Why cannot the existing schedules work for them?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they specifically requested to power on windows instances for their patch slot on the monday after the second tuesday at 11:30pm, as their patch slot is Tuesday 12a - 6a.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they specifically requested to power on windows instances for their patch slot on the monday after the second tuesday at 11:30pm, as their patch slot is Tuesday 12a - 6a.

We need to document these justifications with an eye towards standardized schedules. This is a what, not a why.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they specifically requested to power on windows instances for their patch slot on the monday after the second tuesday at 11:30pm, as their patch slot is Tuesday 12a - 6a.

We need to document these justifications with an eye towards standardized schedules. This is a what, not a why.

Don: How about having customers who want a custom schedule to be required to submit a ticket through Service Now with a Business Justification and approval routing process before it gets implemented? That way there's an option for the customer to request one but that it doesn't guarantee automatic implementation of the request.


# Tagging Examples

Expand All @@ -105,11 +113,11 @@ Example: keep a production dependency running continuously.

If no approved schedule matches your requirement:

1. Open a request with Cloud Infrastructure and include:
* account and region
* resource identifiers
1. Open a request with CSVD-CLOUD for a Server Change Request and include:
* resource types
* required start/stop windows
* business justification and expected duration
* business justification

1. Use `always-on` only when there is a validated operational requirement.
1. Do not create ad hoc schedule values; unapproved values are not supported.

Expand Down