Alerts and budget
ScaleBop sets up two kinds of warning, both in your AWS account. ScaleBop doesn’t receive the alerts or read your metrics.
- Alerts for each project: CloudWatch alarms and a dashboard, in the CDK stack in the project’s repository.
- A monthly budget for your whole AWS account: one AWS Budgets alert covering everything in the account, set once in ScaleBop’s account settings.
What you get
Section titled “What you get”| Signal | What it means | First step |
|---|---|---|
| ALB 5xx rate (container apps) | Your app or load balancer is returning many server errors | Check recent deploys and application logs in CloudWatch Logs |
| Unhealthy targets | A task is failing the health check | Confirm the health path and that the container listens on the expected port |
| No healthy task | Nothing is registered behind the load balancer | Check ECS service events and the latest task stopped reason |
| CloudFront 5xx rate (static and Next.js) | CloudFront is serving many errors to visitors | Check S3 origin paths and any /api proxy configuration |
| Budget alert (optional) | Your account’s spend reached 80% or 100% of the budget, or the month’s forecast went over it | Review Cost Explorer; budget data can lag by about a day |
Alarms notify an SNS topic in the same region as the alarm. CloudFront alarms use a topic in us-east-1.
Project alerts
Section titled “Project alerts”Confirm your email
Section titled “Confirm your email”When you save a project’s alert email, AWS sends a Subscription Confirmation message. Open it and click Confirm subscription before alarms can reach you.
Change the alert email
Section titled “Change the alert email”In ScaleBop, open your project, edit Alerts, then Redeploy production so GitHub Actions passes the new email to CDK.
Without ScaleBop, edit the repository Actions variable SCALEBOP_ALERT_EMAIL, then run the deploy workflow.
Monthly budget
Section titled “Monthly budget”Set it in ScaleBop under Account → AWS budget: a monthly amount in US dollars and an email. ScaleBop creates the budget in AWS Budgets, named ScaleBop-monthly, and saving takes effect straight away; nothing needs redeploying. Redeploying or deleting a project doesn’t touch it, and changing the amount keeps its history.
- The budget covers your whole AWS account, including anything you run outside ScaleBop.
- Budget emails don’t need confirming.
- Billing data can lag by about a day, so it’s an early warning, not a hard limit on spending.
- To change or remove it without ScaleBop, edit or delete
ScaleBop-monthlyin the AWS Budgets console.
ScaleBop needs version 47 or later of the AWS connection stack to manage the budget. If your connection is older, ScaleBop shows a link to reinstall it (same stack name and External ID) when you save.
Budgets from before
Section titled “Budgets from before”Projects used to have their own budget in their CDK stack. That budget is removed the next time the project’s setup is updated and deployed. If you set a cap on a project, ScaleBop fills it in on the account budget form for you, but nothing is created until you save.
One project’s spend
Section titled “One project’s spend”Every stack ScaleBop generates for a project carries the scalebop:project tag, set to the project’s stack name. To see one project’s costs, activate scalebop:project as a cost allocation tag in the AWS Billing console (management account), then filter Cost Explorer by it. Only costs after activation are tagged.
Remove monitoring
Section titled “Remove monitoring”Delete the alarm, dashboard and SNS topic resources from infra/lib/generated-app-stack.ts (and monitoring-us-east-1-stack.ts when present), or run Update setup after ScaleBop removes them from the generated templates, then deploy. Remove the account budget under Account → AWS budget.