Origin-only access is the real win when putting object storage or a private load balancer behind a distribution: lock the bucket or security group so only the distribution principal can fetch, keep viewer TLS and origin TLS as separate trust domains, and align SNI with the origin hostname the leaf actually presents. Prefer OAC over legacy OAI for S3, put ALB or EC2 origins on an origin protocol policy that fails closed on name mismatch, and keep Cookie plus Authorization out of the public cache key so a private path cannot explode cardinality or poison shared HITs.
Ops prove-out after tightening origin access: hit a warm public object twice and expect MISS then HIT with Age climbing under a stable host-path key; then force an origin fetch on a cold path and confirm the distribution completes the origin handshake without certificate errors. Deny a direct origin dial that bypasses the distribution and confirm it fails before any body returns. If only some POPs fail, check whether a second origin or failover target still presents a different chain than the primary — mixed trust stores look like flaky edges when the real issue is origin TLS drift.