R2 Write Test
Diagnostic: attempt a test write to R2 and verify it persists.
ADMIN-ONLY, and every boto3 call runs in a worker thread under a hard budget. Both properties are load-bearing, not hygiene:
This handler previously made FIVE synchronous boto3 calls (put_object,
get_object, Body.read(), list_objects_v2, delete_object) directly
on the event-loop thread, with no auth. botocore’s defaults are 60s connect
- 60s read, so ONE anonymous request to a wedged R2 blocked the entire
single-worker API for minutes —
/healthincluded, since a blocked loop thread cannot answer even a static dict. That is the same symptom as the 2026-07-22 outage and it was reachable by any unauthenticated caller.
A dedicated single-thread executor keeps the loop free WITHOUT letting
repeated admin retries occupy the shared default executor. The wait_for
still bounds only the RESPONSE, not the work — if the thread times out it
keeps running until boto3’s own timeout budget fires, and new probes are
rejected until that worker finishes.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Response
Successful Response