[Solved] An API Gateway method integration returns a 502 Bad Gateway error. What is the most common reason? — Ans: The backend endpoint is unreachable or returns invalid response | AWS

AWS - API Gateway

An API Gateway method integration returns a 502 Bad Gateway error. What is the most common reason?

AThe API Gateway method is not deployed

BThe API Gateway cache is full

CThe client sent a malformed request

DThe backend endpoint is unreachable or returns invalid response

Step-by-Step Solution

Solution:

Step 1: Understand 502 Bad Gateway
502 means API Gateway could not get a valid response from backend.
Step 2: Identify common causes
Backend unreachable or returning invalid data causes 502; deployment issues cause 404 or 403.
Final Answer:
The backend endpoint is unreachable or returns invalid response -> Option D
Quick Check:
502 error = backend failure [OK]

Quick Trick: 502 means backend failed or unreachable [OK]

Common Mistakes:

MISTAKES

Master "API Gateway" in AWS

9 interactive learning modes - each teaches the same concept differently

More AWS Quizzes

An API Gateway method integration returns a 502 Bad Gateway error. What is the most common reason?