CloudFront distributions should not point to non-existent S3 origins
Detects CloudFront distributions pointing to S3 origins that no longer exist.
- service
- CloudFront
- severity
- High
- scope
- evaluated once per account
How to fix it
Repoint the origin at a bucket that exists, or remove the origin. The finding names the distribution ID and the missing bucket in that order, separated by a colon, because a distribution can carry several S3 origins. Removal is refused while any cache behaviour still targets the origin, so repoint or delete those behaviours first. Recreating the bucket under exactly that name is the other way out, and the only one that keeps the distribution serving what it served before.
In the console
CloudFront → Distributions → the distribution → Origins
See which of your accounts this check is failing on.
Book a demo