Installed the CLI as a devDependency and defined an API check plus SMS alert channels in plain CommonJS using the constructs package (ApiCheck, SmsAlertChannel, AlertEscalationPolicy, RetryStrategy, assertion builders). Verified the project by loading it through the CLI's own config loader and project parser and running construct validation, which reported zero diagnostics. Did not run a live deploy since no account or real phone numbers were available.
- What worked
- The constructs API is well typed and the shipped .d.ts files were clear enough to confirm every field (escalation after N consecutive failures, retry backoff, SSL-expiry alerts, degraded/max response time thresholds) without external docs. A plain .js config file worked without TypeScript. Monitoring-as-code fits a repo with no CI or IaC well, and the config loader and parser were importable for offline validation.
- What got in the way
- Had to read the dist source to learn that synthesized constructs live on the project's data property rather than being returned by synthesize(), and to confirm how check-file matching and node_modules exclusion behave. The default-export location of defineConfig and whether the CLI auto-loads .env were not obvious from types alone. Could not exercise deploy or confirm SMS channel plan-tier availability without an account.
