Stop development EC2 instances daily at 21:00 and start them at 08:00 Japan time. Approved Systems Manager Automation runbooks include target checks and result notifications.
Reuse those runbooks without a continuously running scheduling server. Start the API invocation within the specified minute; second-level start and EC2 operation completion times are not requirements. Required roles and instances are ready.
Which TWO components meet the requirements?
Use Asia/Tokyo schedules to invoke StartAutomationExecution with the approved runbook and its inputs.
Detailed explanation
Direct calls are possible but bypass the required runbook checks and notifications.
Direct calls are possible but bypass the required runbook checks and notifications.
Metric thresholds do not define the required local-time schedule.
Metric thresholds do not define the required local-time schedule.
Cron expressions and the time zone define the invocation minute. Disabling the flexible window does not guarantee a second-level start or immediate EC2 operation completion.
Cron expressions and the time zone define the invocation minute. Disabling the flexible window does not guarantee a second-level start or immediate EC2 operation completion.
UTC and Asia/Tokyo differ by nine hours. UTC 21:00 is 06:00 the next day in Japan; UTC 08:00 is 17:00 in Japan.
UTC and Asia/Tokyo differ by nine hours. UTC 21:00 is 06:00 the next day in Japan; UTC 08:00 is 17:00 in Japan.
A universal target passes DocumentName and runbook-defined Parameters, retaining the approved procedure.
A universal target passes DocumentName and runbook-defined Parameters, retaining the approved procedure.
Check official documentation
Compare the following points with the official documentation.
Review universal targets, time zones, and the StartAutomationExecution request parameters.
Official references
What to confirm
Distinguish scheduling and API inputs from authorized EC2 operations within the runbook.
Key points
- EventBridge Scheduler
- SSM Automation
- EC2 instance state
Notes
- Environment: AWS SOA-C03 exam guide and the linked AWS documentation
- Reviewed against the linked AWS documentation on 2026-10-08.
Foundation review
Connect time to API inputs
Use cron(0 21 * * ? *) for stop and cron(0 8 * * ? *) for start, evaluated in Asia/Tokyo with FlexibleTimeWindow Mode OFF. Invocation has 60-second precision; distinguish starting the API within that minute from completing EC2 operations. The universal target passes DocumentName and runbook-defined Parameters to StartAutomationExecution. Correct time alone does not repair an incorrect API or input.
Separate execution permissions
The Scheduler role starts Automation; the runbook role performs EC2 and notification actions. Direct API calls can bypass required procedure steps.