An application calls API Gateway, Lambda, and DynamoDB, and the team needs to find where requests are slow.
Visualize the path across services.
Which service is most appropriate?
AWS X-Ray analyzes distributed traces and service maps to locate latency across services.
Detailed explanation
CodePipeline coordinates development and deployment stages, not runtime traces.
CodePipeline coordinates development and deployment stages, not runtime traces.
X-Ray traces request paths and latency across distributed services.
X-Ray traces request paths and latency across distributed services.
SNS distributes notifications and does not trace request paths.
SNS distributes notifications and does not trace request paths.
Budgets monitors cost and usage thresholds.
Budgets monitors cost and usage thresholds.
Check official documentation
Compare the following points with the official documentation.
AWS X-Rayの公式概要でトレース、セグメント、サービスマップを確認する。
Official references
What to confirm
分散リクエストの遅延調査へX-Rayを選べる。
Key points
- AWS X-Ray
- Distributed tracing
- Service map
Notes
- Environment:
- AWS service features and names can change; confirm current behavior in the official AWS documentation.
Foundation review
Choose by purpose
A notification, queue, support case, build stage, desktop, browser, frontend, and IoT device have different service boundaries.
Separate adjacent services
Services may work together, but the question asks which one owns the required capability.