AWS solutions documentation change
Summary
Added an 'Important' section warning about misconfigured schedules causing unexpected costs and providing guidance on verifying schedule configurations, error handling, and monitoring tags
Security assessment
This change addresses operational and cost management concerns, not security vulnerabilities. It focuses on preventing financial waste due to misconfigurations but doesn't mention security vulnerabilities, access control issues, or data protection concerns. The guidance is about proper configuration monitoring rather than security hardening.
Diff
diff --git a/solutions/latest/instance-scheduler-on-aws/operator-guide.md b/solutions/latest/instance-scheduler-on-aws/operator-guide.md index 23666f4c0..dc48910e5 100644 --- a//solutions/latest/instance-scheduler-on-aws/operator-guide.md +++ b//solutions/latest/instance-scheduler-on-aws/operator-guide.md @@ -12,0 +13,17 @@ This guide is intended for users and operators of this solution and contains det +###### Important + +Misconfigured schedules can result in instances running continuously and incurring unexpected costs. Before applying schedules to your resources, verify the following: + + * The schedule name in the resource tag exactly matches a schedule defined in the configuration table. Misspelled or nonexistent schedule names will result in an `UnknownSchedule` error and the instance will not be stopped by the scheduler. Check for the `IS-Error` tag on your resources to identify this condition. + + * If `stop_new_instances` is set to `false`, instances that are running outside of a scheduled period when first tagged will not be stopped until the next scheduled stop transition. This can result in instances running longer than expected. + + * If `retain_running` is set to `true`, instances that are manually started before a running period begins will not be stopped at the end of that period. This is by design, but can lead to instances running indefinitely if not monitored. + + * When using `enforced: false` (the default), the scheduler will not restart instances that are manually stopped during a running period, and will not stop instances that are manually started outside of a running period after the initial stop transition. + + + + +We recommend enabling [informational tagging](./monitor-the-solution.html#informational-tags) (enabled by default) and periodically reviewing the `IS-Error` and `IS-LastAction` tags on your resources to confirm that scheduling is operating as expected. +