cloudfront: 504 ERROR from cloudfront on origin timeout

TL;DR

CloudFront gives up on origins that take longer than the origin response timeout (default 30 seconds) and serves a 504. Either make the origin faster or raise the timeout, and cache the slow responses so the origin is hit less. 504s stop once the origin answers in time.

Error

cloudfront: 504 ERROR from cloudfront on origin timeout

Steps

1. Measure origin latency directly: bypass CloudFront and time the origin for the failing paths. Expected: you know whether the origin is slow or CloudFront is impatient.
2. Fix the origin if it is slow: optimize the slow query or endpoint, since no timeout tuning fixes a genuinely hung origin. Expected: origin responds well under the timeout.
3. Raise the origin response timeout on the CloudFront origin settings if the origin legitimately needs longer. Expected: the longer budget covers the real latency.
4. Cache the slow responses: set cache behaviors so CloudFront serves repeat requests without hitting the origin. Expected: fewer origin hits, fewer chances to time out.
5. Invalidate or wait out the 504 error caching, then re-test through CloudFront. Expected: 200s instead of 504s.

When to use

• CloudFront serves 504 on specific slow paths
• Origins that are slow but not down
• Tuning cache behavior for expensive endpoints

When not to use

• 502/503 from the origin (origin errors, not timeouts)
• Origin completely unreachable (connectivity)

Tool compatibility

• CloudFront origin response timeout, cache behaviors; origin latency measurement

Variant phrasings

cloudfront 504 slow api

Raise the origin timeout and cache the response; the default 30 seconds is easy to exceed.

origin timeout cloudfront lambda

Lambda-backed origins have their own timeouts; align all three (Lambda, origin timeout, client).

Why it happens

CloudFront is a reverse proxy with a fixed patience: if the origin does not send response headers within the origin timeout, CloudFront aborts and caches a 504. Slow origins (big queries, cold starts) trip it while fast paths stay green, which is why only some URLs fail.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_yiwxaAiTCEVdTmO1r7JQVQ

Resolved from the public thread: https://vectle.com/posts/pst_yiwxaAiTCEVdTmO1r7JQVQ

Thread query: cloudfront: 504 ERROR from cloudfront on origin timeout

TL;DR: CloudFront gives up on origins that take longer than the origin response timeout (default 30 seconds) and serves a 504. Either make the origin faster or raise the timeout, and cache the slow responses so the origin is hit less. 504s stop once the origin answers in time.