Schedule AWS ECS Services: Scale to Zero Outside Business Hours

Most of what teams spend on ECS Service Scaling in non-production is spent while nobody is watching. In a development, staging, or QA account these resources are billed for every hour they exist, but the people who use them work a fraction of those hours. Nights, weekends, holidays, and the long tail of “we’ll get back to that environment next sprint” all meter at full price.

ZopNight closes that gap by scheduling your ECS Service Scaling to run on your team’s hours and stop the rest of the time, without touching your data and without a migration. It is the most direct lever in FinOps, and for teams comparing tools it is where ZopNight pulls ahead of dashboard-first platforms like CloudHealth.

Why ECS Service Scaling cost more than they should

Cloud providers bill ECS Service Scaling by the hour whether or not anyone is using them, and most non-production fleets default to running 24/7 out of habit rather than need. At typical on-demand rates ($0.05–$3.00/hr) an always-on instance quietly bills the same on a Tuesday afternoon as it does at 3 AM on a Sunday.

Here is the shape of it. Say a box runs at a typical on-demand rate of $0.17 an hour. Left on around the clock that is about $124 a month, because a month is roughly 730 hours. Confine it to a single-shift work week, about 50 hours, and you pay for 50 hours instead of 730. Your own rate and hours will differ, but the ratio is the point: in non-production, most of the meter runs while nobody is working.

The instinct is usually to reach for a smaller instance type. But rightsizing only helps a resource that is genuinely too big; it does nothing for a correctly-sized resource that simply runs when no one is around. The larger, easier win is refusing to pay for the hours nobody is working, and it carries none of the performance risk of down-sizing a box that might spike tomorrow.

Stopping and starting ECS Service Scaling safely

ZopNight handles the Scale service desired count to zero via ECS API on every ECS Service Scaling in scope, in dependency order so nothing comes up before what it depends on. A scheduled stop preserves your data exactly as a normal power-off would; ZopNight never terminates or deletes the resource, and idle detection watches CPU, network, and disk signals to surface the ECS Service Scaling that are running but doing nothing.

In practice the setup is: Connect your AWS account. ZopNight discovers ECS clusters, services, and task definitions; Create schedules per service or per cluster (e.g., scale to zero at 8 PM); ZopNight sets service desired count to zero, tasks drain gracefully; Before working hours, ZopNight restores desired counts and verifies task health.

If you run ECS Service Scaling you probably also run EC2, EKS, APP Runner, and scheduling them together is where the dependency ordering earns its keep. Related reading: scheduling and cost optimization.

How ZopNight schedules ECS Service Scaling

The loop that does this is deliberately mechanical, and it starts read-only. You connect AWS with a read-only role, and ZopNight discovers every ECS Service Scaling across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled.

Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like “dev-cluster” or “staging-db” so a whole environment follows one cadence.

Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a ECS Service Scaling ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it.

Beyond the schedule: recommendations, rightsizing, and showback

Scheduling is the fastest lever, but it is one of several. ZopNight ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147) that flag idle, oversized, and orphaned resources, and each recommendation shows the current monthly cost next to the estimated optimized cost so you act on the largest first. 124 of those recommendations are wired to act end to end, 28 one-click and 96 guided: one-click actions run immediately behind an admin-approval gate, and guided actions add a type-to-confirm review so you check the change before it lands. You mark a recommendation applied once you act, or dismiss the ones that do not fit.

Idle detection reads CPU, network, and connection metrics over a rolling window to separate a genuinely idle resource from one with real but intermittent traffic. Rightsizing is guided and computed from measured utilization over a real window, never a flat 24/7 assumption, so the projected figure matches the bill you actually see. For steady-state fleets, VM autoscaling runs in one of three modes derived from the credential’s permissions: monitor, recommend, or autopilot.

What is left after optimization gets attributed rather than hidden. Showback splits shared cost across owning teams and rolls up by cloud tag, GCP label, or Azure tag, with a Sankey cost-flow view that traces spend across provider, account, type, and team and a savings overlay that points straight at the reclaimable flows. A daily anomaly job writes root-cause markers onto the cost trend, an instance resize, a new resource, a reservation expiry, a failed schedule, so a spike explains itself instead of prompting a manual hunt. And 43 read-only tools expose the same data to an AI assistant over MCP, so you can ask an assistant in Claude, Cursor, or Codex for the same numbers.

Best practices that keep the savings

A few habits separate teams that hold onto the savings from teams that watch them drift back:

• Start with non-production and prove it there. Development, staging, QA, and demo environments carry almost no risk and the largest idle share, so they are the right place to build confidence before anyone considers production.
• Schedule by group, not by hand. Bundling an environment into a group like “staging” means one cadence covers every resource in it, and resources you add later inherit the schedule instead of being quietly forgotten.
• Use overrides instead of disabling schedules. When a late deploy needs a box overnight, a time-boxed override with a written reason keeps the schedule intact and expires on its own, so a one-off exception never becomes a permanent leak.
• Watch the audit trail and notifications. Every start, stop, and failure is logged and can post to Slack, Teams, or Google Chat, so a failed action is visible the moment it happens rather than discovered on the next invoice.
• Treat it as an operating rhythm, not a cleanup. The teams that keep the bill down review recommendations on a cadence and let the automation run continuously, instead of a one-off spring-clean that snaps back the moment attention moves on.

Getting started

Getting started is intentionally low-stakes:

• Connect AWS with a read-only role. Nothing is scheduled or changed at this stage.
• Let ZopNight discover your ECS Service Scaling 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.