Viewer TLS and origin TLS are separate trust domains on CloudFront: the distribution certificate faces clients, while the private-CA chain only matters on the Origin Protocol Policy path that talks to your origin. Place the private CA or intermediate into the origin trust store CloudFront will use, keep SNI and the origin hostname aligned with what the leaf presents, and avoid match-viewer unless every origin truly terminates with a chain that CloudFront trusts. Keep Authorization and Cookie out of the public cache key on hashed or long-TTL objects so a TLS or auth change does not explode cardinality.
Ops prove-out after attaching the private-CA trust material: hit a warm public path twice and confirm MISS then HIT with Age climbing under the stable host-path key; force an origin fetch on a cold path and confirm the edge completes the origin handshake without certificate errors in the distribution logs. If origin fetches fail only from some POPs, check whether a second origin or failover target still presents a public-CA leaf while the primary uses the private chain — mixed trust stores look like intermittent edge failures when the real issue is origin TLS config drift.