Nightly jobs that snapshot logs, rotate permit extracts, and start assessor batches currently run from cron on a shared jump host that assumes roles into several department accounts. Which integration modernization should replace that pattern?
Select an answer to reveal the explanation.
Short Explanation
A jump box with crontab is a sticky note on one person's monitor. EventBridge is the county clock that can wake jobs in many accounts without that host. When a new department joins, add a rule—not another SSH key.
Full Explanation
Nightly jobs that snapshot logs, rotate permit extracts, and start assessor batches from cron on a shared jump host that assumes roles into several department accounts should be replaced with Amazon EventBridge Scheduler or scheduled rules that invoke jobs across accounts. That integration modernization removes SSH-key sprawl and centralizes civic schedule control. Keeping cron on the jump host and adding more SSH keys as new accounts join the organization fails scalable multi-account operations. Emailing a shared mailbox when it is time for an operator to start each job by hand fails automation and night reliability. Placing a Windows Task Scheduler instance in every VPC as a permanent control plane fails by multiplying unmanaged schedulers. Exam caveat: EventBridge Scheduler/rules replace jump-host cron for cross-account jobs. Operational check: define schedules in EventBridge, invoke Lambda/Step Functions/ECS per account via roles, alarm on missed invocations, retire jump-host cron, and document the night schedule for the PMO. Document the decision in the municipal architecture decision record and re-verify controls after the first production wave so auditors see continuous improvement, not one-time tribal knowledge.