You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
[3.1.0] -- 2025-12-18
Added
Added Support for License Manager controlled EC2 instances
Added IS-MinDesiredMax control tag to ASGs to simplify management of ASG resources
Added support for retrying Insufficient Capacity Errors on EC2 with different instance sizes
Use IS-PreferredInstanceTypes control tag to specify acceptable instance types that can be used
Added IS-GlobalEvents (in hub) and IS-LocalEvents (in all targets) event buses that will output the following events:
Resource Registered whenever a resource is registered for scheduling
Scheduling Action whenever a resource is started/stopped by the scheduler
Changed
Instance Scheduler now listens for tagging events and tracks managed instances in an internal registry table
Optimized scheduling orchestration to improve scaling performance for larger deployments.
Managed regions is now defined per-account in the remote stack rather than globally on the hub stack
Instance Scheduler will now apply informational tags to resources during scheduling:
IS-ManagedBy -- indicates location of Instance Scheduler Hub Stack
IS-LastAction -- displays the last successful action taken by instance scheduler
IS-Error -- displays error code when errors occur during scheduling
IS-ErrorMessage -- displays additional information about the most recent error code
Cleaned up Operational Insights dashboard and added widgets to display ASG scheduling metrics
Brought ASG scheduling flows inline with other scheduling flows
Moved logs into dedicated -scheduling-logs and -administrative-logs log groups
Restructured logs to use structured-logging optimized for log-insights queries and provided pre-canned
queries that can be used in the CloudWatch Log Insights console.
Removed
Listing member accounts via an SSM parameter (passing {param: ssm-param-name} to the accounts parameter on the hub stack)
is no longer supported.
Scheduled instance resizing (defining period-name@size in a schedule)
is no longer supported.
Started/Stopped tags configuration parameter on hub stack has been removed (replaced by informational tagging feature)
Deployments of more than 40 accounts must now use organizations mode
EnableXXXScheduling properties removed -- Service-specific scheduling is now handled automatically in response to tagging events
