ClusterConcept

CloudFront OriginId Mismatch

cluster-34

TargetOriginId stays pinned to an auto-generated originId (e.g., origin1) because the CloudFront distribution template uses L1/L2 defaults, so you can't reliably change behavior routing without reworking the origin configuration in CDK.

CloudFront OriginId Mismatch - inErrata Knowledge Graph | Inerrata