ES /docs

CloudFront origin connection failure — 504 Gateway Timeout

Service
aerial-map-service
Occurrences
10
Status
Reported
Confidence
80%
Actionability
52%
Cluster ID
12ffb1b3-baf1-44e7-b508-e3ed7f1aaca3
First Seen
2026-04-10 00:41 UTC
Last Seen
2026-06-23 15:09 UTC
Actions

CloudFront origin connection failure — 504 Gateway Timeout

What Happened#

2026-04-23 15:28~16:04 KST 사이에 aerial-map-service의 preprocess 및 postprocess Fargate 태스크가 Cupix API 호출 시 CloudFront로부터 504 Gateway Timeout 응답을 받아 실패했다. 이 클러스터는 preprocess fail 1건을 포함하며, 같은 시간대에 postprocess fail도 6건 발생했다 (별도 fingerprint).

Quick Facts#

Field Value
exception.message 504 Gateway Timeout ERROR - Generated by cloudfront (CloudFront) HTTP3 Server
top_frame src/preprocess/index.ts:175
runtime Node.js 20 on ECS Fargate (2048 MB)
env production, us-west-2

Timeline#

  1. 2026-04-23 15:28:21 KST — 최초 postprocess 504 에러 발생 (aerial map ID 불확인)
  2. 2026-04-23 15:49:57 KST — aerial map 334의 preprocess 성공 (정상 요청 확인)
  3. 2026-04-23 15:51:19 KST — aerial map 334의 preprocess fail (504 Gateway Timeout) - 이 클러스터의 대표 에러
  4. 2026-04-23 15:52:17 KST — preprocess-check Lambda가 Fargate 태스크 실패 감지 (ExitCode: 1, aerial map 332)
  5. 2026-04-23 15:58:34~16:04:47 KST — postprocess에서도 동일 504 에러 반복 발생
  6. 2026-04-23 16:02:05 KST — aerial map 333의 postprocess-check 성공 (정상 요청 확인)

Scoring#

Confidence 80% · Actionability 52%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 11 code refs, 6 log queries
Code path explicitness 3/3 11 file:line refs
Log evidence 2/3 section, query
RCA structure 3/3 3/3 sections
Revision history 0/3 0 revision(s)
Agent execution 3/3 success

Actionability#

Dimension Score Detail
Fix complexity 5/5 trivial
Affected files 1/5 11 file(s)
Single repo 1/3 3 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 3/3 no external deps
Data migration 3/3 no migration