Bring existing AWS Auto Scaling Group policies under ZopNight observation without overwriting them. Adopt-or-replace flow keeps the previous config and supports byte-accurate rollback.
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 15 minutes. Before you start you will want: AWS account connected with read_write permissions for source=recommended; An ASG with at least one existing scaling policy; A ZopNight account.
The steps
- Open the Create Autoscaler wizard.
- Read the source field on each policy.
- Choose Adopt or Replace.
- Check the editable flag.
- Edit triggers auto-promote.
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.
What happens on Remove for an adopted policy?
Adopted policies skip the write path entirely. Remove flips the row out of management without any AWS API call. Replace policies restore the captured rawSpec byte-accurately via internal.AutoscaleRestoreState.
Why does ZopNight refuse Replace on PredictiveScaling?
Predictive scaling cannot be reconstructed from a serialised rawSpec because the predicted capacity model lives in AWS. ZopNight refuses zero-AWS-mutation rather than risk silent loss of the user predictive model.