Repository navigation
[bespoke] 4. Confirm the alert emails #21
Description
Order: step 4 of 11, after #20. The first four make the API usable; the rest make it ready for real customers.
- Budget and anomaly alerts: SNS sent a subscription confirmation ("AWS Notification - Subscription Confirmation") for the
substratal-billing-alertstopic toadronhall@proton.me. Click Confirm subscription; until then the $75 warning, the $150 hard stop, and anomaly alerts reach no one. - Operational alarms (5xx rate, Lambda errors and throttles, Aurora near capacity, webhook DLQ, security log): the
alarm_emailTerraform variable is empty, so these alarms have no recipient. Decide the address; setting it is a one-line change toinfra/terraform/prod/variables.tfand a confirmation click after the next deploy.
Moved from remaining_manual_steps.md, which this set of [bespoke] issues replaces.
Activity
Adron commentedon Oct 22, 2026
Operational alarms now go to
adronhall@proton.me(PR #64, deployed 2026-10-22). Two SNS subscription confirmations are now waiting in that inbox: thesubstratal-billing-alertstopic and the operational alarms topic. This issue can close once both are confirmed.Adron commentedon Oct 23, 2026
Both alert topics have a confirmed email subscription (substratal-prod-alarms and substratal-billing-alerts; neither is PendingConfirmation). Checked 2026-10-23.