# How to Set Up Cloud Cost Alerts: Step by Step

> How to Set Up Cloud Cost Alerts. A practical walkthrough with ZopNight: read-only setup, production excluded by default, reversible at every step.

Source: https://zop.dev/learn/how-to/set-up-cloud-cost-alerts
Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, how-to, learn

---

Configure cloud cost alerts to catch budget overruns and anomalies early. Step-by-step guide for AWS, GCP, and Azure cost notification setup.

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 10 minutes. Before you start you will want: A ZopNight account connected to your cloud accounts; Notification channel (Slack, Teams, email) configured; Defined budget targets.

## The steps

1. Define budget thresholds.
2. Configure alert channels.
3. Set anomaly detection.
4. Create escalation rules.

## 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](https://zop.dev/learn/finops) guide covers where it fits, and the [AWS EC2 scheduling](https://zop.dev/zopnight/aws/ec2) 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.

## Frequently asked questions

### How quickly do cost alerts fire?

ZopNight checks spending against budgets every 6 hours. Anomaly detection runs daily. For real-time resource-level alerting, alerts fire within minutes of a threshold being crossed.

### Can I set different budgets for different environments?

Yes. Define separate budgets for dev, staging, and production. Each can have its own thresholds, notification channels, and escalation rules.