# Energy on AWS: Cut Cloud Cost > How Energy & Utilities teams cut non-production AWS waste with ZopNight. Scheduling first, read-only setup, production excluded by default. Source: https://zop.dev/industries/energy/aws Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, industry, energy, aws --- Energy companies running SCADA platforms, grid analytics, and renewable monitoring systems can schedule non-production workloads for business hours only. For Energy & Utilities teams on AWS, the opportunity is structural: fast-moving teams stand up more non-production environments than they retire, and each one bills around the clock on AWS while being used a fraction of the time. ## What drives AWS cost in Energy The recurring pressure points: - SCADA platform development environments. - Grid analytics processing requires significant compute. - Renewable energy monitoring development and testing. - Compliance requirements for utility infrastructure. On AWS these show up as EC2, RDS, and EKS that run through nights and weekends nobody is working. ## How ZopNight helps Discover the full non-production AWS footprint, schedule it to your working hours, add idle detection and guided rightsizing, then attribute the rest with showback. ZopNight ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147) and starts read-only, so an IT Director or Cloud Architect can stand it up without a change-management fight. See it on [AWS EC2](https://zop.dev/zopnight/aws/ec2). ## How ZopNight schedules non-production resources 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 non-production resources 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 non-production resources 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. ## 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 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. ## Frequently asked questions ### Where do Energy teams on AWS start? Scheduling non-production AWS resources to business hours, then idle detection and rightsizing. The figure depends on your fleet; ZopNight measures it against real usage. ### Will this affect production? No. Production is excluded by default; only the non-production AWS resources you choose are scheduled.