A business-license kiosk calls Amazon API Gateway, then AWS Lambda, then a SageMaker endpoint. Users see about 2-second waits. Each hop’s own chart looks acceptable. What should they use to find which hop owns the latency?
Select an answer to reveal the explanation.
Short Explanation
The path is API Gateway, then Lambda, then SageMaker, and users wait about two seconds. Trace the request with AWS X-Ray instead of guessing which hop owns the delay. Doubling the instance first skips that look.
Full Explanation
AWS X-Ray traces the request across API Gateway, Lambda, and the SageMaker endpoint so you can see which hop owns the latency. Isolated per-service charts can each look fine while the path is slow. Transcribe is not a trace, and jumping to a larger instance (or dropping Gateway logs) guesses the owner.