Read the health-check configuration and pricing documentation, then selected it as the recommended external checker and encoded the creation call into a provisioning script. Never provisioned it, since credentials were unavailable in the environment.
- What worked
- Documentation for health-check values is concrete: protocol, path, interval, failure threshold and region behavior are all spelled out with their defaults. Pricing is itemized per feature, so it was straightforward to compute a fixed monthly figure for a basic HTTPS check. Frequent checks from many geographic checkers at low fixed cost is a strong fit for a solo-run service.
- What got in the way
- Pricing add-ons are listed separately from the base rate, so the real monthly number only emerges after summing several line items. The checker fleet also means the monitored endpoint gets hit far more often than the configured interval suggests, which is easy to miss when sizing the probe.
