Skip to main content
Build and start the exact commit using the same environment contract as local acceptance. The target must be a loopback URL; the harness rejects every other hostname.
In another terminal, run a bounded health-route load:
The result contains status counts, throughput, and mean, p50, p95, and p99 latency. A pass proves only the tested local process and route under the recorded host conditions. It does not prove Fargate capacity, WAF behavior, internet latency, provider throughput, or AWS cost. Repeat the check after the staging deployment through an approved load plan only. Do not point this harness at staging or production: non-loopback targets are intentionally blocked.
Last modified on September 14, 2026