ES /docs

AwsS3Manager::uploadDirectoryByCredential | upload failed - {"message":"Connection timed out after 1

Service
cupixworks-pano-postprocessor-instance
Occurrences
84
Status
Reported
Confidence
85%
Actionability
44%
Cluster ID
c9f74243-a4d0-4453-b5c0-9fb2f942c396
First Seen
2026-04-16 12:07 UTC
Last Seen
2026-06-26 05:22 UTC
Datadog↗ Slack↗
Actions

AwsS3Manager::uploadDirectoryByCredential | upload failed - {"message":"Connection timed out after 1

What Happened#

2026-05-22 14:35~16:11 UTC 사이에 eu-central-1 리전에서 실행 중인 pano-postprocessor 인스턴스가 me-central-1 (UAE) S3 버킷으로의 파일 업로드 시 반복적인 connection timeout(120초)을 경험했다. hassan-allam 팀의 캡처 3건(36961, 36963, 36966)에서 총 6건의 S3 오류가 발생했으며, 최종적으로 재시도를 통해 모든 304개 파노라마가 성공적으로 처리되었다.

Quick Facts#

Field Value
exception.class TimeoutError
exception.message Connection timed out after 120000ms
top_frame aws-s3.manager.ts:138
env production, eu-central-1 → me-central-1 (cross-region)

Affected Teams#

Team / Domain Error Count Impact
hassan-allam 6 파노 리사이즈 업로드 지연 (최종 성공, 데이터 손실 없음)

Timeline#

  1. 14:35:25Z — 첫 번째 timeout 발생 (job 101985, capture 36961)
  2. 14:41:42Z — ECONNRESET 발생 (job 102001, capture 36963)
  3. 15:28:54Z — job 102003에서 timeout 발생
  4. 15:49:55Z — 이 클러스터의 첫 번째 에러 (job 102003, capture 36966)
  5. 16:03:34Z — 이 클러스터의 두 번째 에러 (동일 세션)
  6. 16:11:31Z — S3 InternalError 발생 (동일 세션)
  7. 16:17:04Z — job 102003 정상 완료 (304/304 panos, 0 errored)

Scoring#

Confidence 85% · Actionability 44%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 8 code refs, 2 log queries
Code path explicitness 3/3 8 file:line refs
Log evidence 3/3 section, query, pattern
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 6 file(s)
Single repo 1/3 3 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 1/3 external deps found
Data migration 3/3 no migration