AWS Resource Scheduler Alternative: Quick Setup vs ZopNight
Resource Scheduler is the lightest way to schedule EC2 on AWS: a few clicks and a tag. That simplicity is its strength and its limit.
What Resource Scheduler is
Resource Scheduler is a configuration type in AWS Systems Manager Quick Setup. AWS’s user guide (Resource Scheduler) says you “configure Resource Scheduler to automate the starting and stopping of Amazon EC2 instances”. It “targets Amazon EC2 instances using the tag key and value” that you choose.
The same page covers the practical details:
- There is “no cost to use Quick Setup”, though AWS notes that costs can be incurred by the services the setup uses.
- A configuration can span multiple Regions and accounts (through organizational units).
- It handles “up to 5,000 instances per Region” per configuration.
It also covers what happens when someone intervenes by hand. If a person starts an instance during its off hours, “Resource Scheduler will not stop the instance again”. Likewise, instances that “are manually stopped at a later time” are not started again.
It is not the same as Instance Scheduler on AWS, a separate solution that you deploy from CloudFormation and that also covers RDS, Aurora and ASGs. We compare that one on its own page.
When Resource Scheduler is enough
If what you need is “these tagged EC2 instances off at night, on in the morning”, Resource Scheduler is hard to beat. It is free to configure, built into the console, and needs no stack to maintain. Many teams should start here.
When you outgrow it
The limits come from its scope. AWS documents it for EC2 only, so an RDS instance, an EKS node group or an ECS service behind those instances needs a different mechanism. A tag also carries no reason and no expiry. A manual start tonight leaves the instance running with no reason attached and no end time.
ZopNight fills those gaps:
- Every tier of an environment on one schedule. One schedule covers EC2 plus RDS, EKS, ECS services, ASGs and Lambda. In a resource group, members start in tiers with per-resource delays, so storage comes up before databases, databases before compute, and compute before apps.
- Overrides with a reason and an expiry. A manual exception becomes an override: keep this resource on until 11 PM, reason “load test”. It expires on its own and notifies your channel when it is set and when it ends.
- A full trail. History shows whether a schedule, an override or a named user started or stopped each resource.
- Clouds beyond AWS. The same model works on GCP and Azure.
| ZopNight | SSM Resource Scheduler | |
|---|---|---|
| Resource types | EC2, RDS, EKS, ECS, ASG, Lambda and more; GCP and Azure | EC2 instances |
| Targeting | Individual resources or resource groups | One tag key and value |
| Manual exceptions | Overrides with reason and expiry | Manually started instance is not stopped again |
| Cost to configure | See zop.dev/pricing | No Quick Setup charge |
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Is AWS Resource Scheduler the same as Instance Scheduler on AWS?
No. Resource Scheduler is a Systems Manager Quick Setup configuration for EC2 instances, targeted by a tag. Instance Scheduler on AWS is a separate solution deployed from a CloudFormation template that also schedules RDS, Aurora and Auto Scaling groups.
Does Resource Scheduler work with RDS?
AWS's Resource Scheduler documentation describes starting and stopping EC2 instances only. For RDS you would use Instance Scheduler on AWS, your own automation, or a tool such as ZopNight.
What happens to an instance someone starts manually after hours?
With Resource Scheduler, AWS says it will not stop that instance again. In ZopNight, the equivalent is an override with a reason and an expiry, so the exception is visible and ends on its own.