# Resource Scheduling: Cut Cloud Cost

> How ZopNight handles resource scheduling across AWS, GCP, and Azure. Read-only setup, production excluded by default.

Source: https://zop.dev/solutions/scheduling
Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, hub

---

Define cron-based start/stop schedules for non-production environments. Dev and staging resources run only during business hours, automatically. ZopNight applies resource scheduling to non-production across AWS, GCP, and Azure, measured against real usage. See it by cloud or by service below, and the discipline in [FinOps](https://zop.dev/learn/finops).

## By cloud

- [AWS Resource Scheduling](https://zop.dev/aws-scheduling)
- [GCP Resource Scheduling](https://zop.dev/gcp-scheduling)
- [Azure Resource Scheduling](https://zop.dev/azure-scheduling)

## By service

- [Resource Scheduling for EC2](https://zop.dev/solutions/aws-ec2/scheduling)
- [Resource Scheduling for RDS](https://zop.dev/solutions/aws-rds/scheduling)
- [Resource Scheduling for EKS](https://zop.dev/solutions/aws-eks/scheduling)
- [Resource Scheduling for ECS](https://zop.dev/solutions/aws-ecs/scheduling)
- [Resource Scheduling for Lambda](https://zop.dev/solutions/aws-lambda/scheduling)
- [Resource Scheduling for ElastiCache](https://zop.dev/solutions/aws-elasticache/scheduling)
- [Resource Scheduling for Redshift](https://zop.dev/solutions/aws-redshift/scheduling)
- [Resource Scheduling for SageMaker](https://zop.dev/solutions/aws-sagemaker/scheduling)
- [Resource Scheduling for EMR](https://zop.dev/solutions/aws-emr/scheduling)
- [Resource Scheduling for ASG](https://zop.dev/solutions/aws-auto-scaling/scheduling)
- [Resource Scheduling for S3](https://zop.dev/solutions/aws-s3/scheduling)
- [Resource Scheduling for EBS](https://zop.dev/solutions/aws-ebs/scheduling)
- [Resource Scheduling for CloudFront](https://zop.dev/solutions/aws-cloudfront/scheduling)
- [Resource Scheduling for DynamoDB](https://zop.dev/solutions/aws-dynamodb/scheduling)
- [Resource Scheduling for App Runner](https://zop.dev/solutions/aws-app-runner/scheduling)
- [Resource Scheduling for Compute Engine](https://zop.dev/solutions/gcp-compute-engine/scheduling)
- [Resource Scheduling for Cloud SQL](https://zop.dev/solutions/gcp-cloud-sql/scheduling)
- [Resource Scheduling for GKE](https://zop.dev/solutions/gcp-gke/scheduling)
- [Resource Scheduling for Cloud Run](https://zop.dev/solutions/gcp-cloud-run/scheduling)
- [Resource Scheduling for Memorystore](https://zop.dev/solutions/gcp-memorystore/scheduling)
- [Resource Scheduling for BigQuery](https://zop.dev/solutions/gcp-bigquery/scheduling)
- [Resource Scheduling for Cloud Functions](https://zop.dev/solutions/gcp-cloud-functions/scheduling)
- [Resource Scheduling for Artifact Registry](https://zop.dev/solutions/gcp-artifact-registry/scheduling)
- [Resource Scheduling for Azure VMs](https://zop.dev/solutions/azure-virtual-machines/scheduling)
- [Resource Scheduling for AKS](https://zop.dev/solutions/azure-aks/scheduling)
- [Resource Scheduling for Azure SQL](https://zop.dev/solutions/azure-sql-database/scheduling)
- [Resource Scheduling for Azure Functions](https://zop.dev/solutions/azure-functions/scheduling)
- [Resource Scheduling for VMSS](https://zop.dev/solutions/azure-vm-scale-sets/scheduling)
- [Resource Scheduling for Databricks](https://zop.dev/solutions/azure-databricks/scheduling)
- [Resource Scheduling for ML Compute](https://zop.dev/solutions/azure-ml-compute/scheduling)

## Frequently asked questions

### Where should I start?

Start with the FinOps overview for the discipline that ties it together, then use the specific guide, cloud, or location page for the task you are on.

### Is production at risk?

No. Production is excluded by default; ZopNight acts only on the non-production resources you choose.

### What access does ZopNight need?

A read-only role to start. Discovery, cost reporting, and recommendations all run read-only, and you enable actions when you are ready.

### Which clouds are supported?

AWS, GCP, and Azure from one platform, including Databricks across all three. Schedules, groups, overrides, and recommendations work the same way regardless of provider.