Use ZopNight Event Readiness to pre-scale ASG, ECS, MIG, and VMSS for a product launch. Cloud-native scheduled actions, no polling, automatic rollback after the launch window.
This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 25 minutes. Before you start you will want: Autoscaler policies on the targets; A pre-launch capacity test or baseline metric for sizing; A ZopNight account with Event Readiness enabled.
The steps
- Plan capacity multiplier or expectedRequests.
- Open Event Readiness and create the event.
- Add scaling targets.
- Schedule and notify.
- Rollback on completion or cancel.
Why this is safe to do today
The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.
If you want the fuller context behind this task, the FinOps guide covers where it fits, and the AWS EC2 scheduling page shows the same loop applied to a specific resource.
Getting started
Getting started is intentionally low-stakes:
- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.
Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Can I cancel after the launch starts?
Yes. Cancel is idempotent. Deterministic scheduleIds keyed on eventId mean re-queue is a no-op and cancel cleanly removes the schedules from every target.
What happens if my DB cannot handle the launch traffic?
ZopNight surfaces sizing recommendations from connection-pool math, but DB tier changes stay with your DBA team. Plan DB scaling separately from the Event Readiness wizard.