An API Gateway, Lambda, and DynamoDB application is slow.
Identify the latency location across the services used by one request.
Which service is most appropriate?
Collect distributed traces with AWS X-Ray to follow a request across services and locate latency or errors.
Detailed explanation
KMS key rotation manages cryptographic keys and is not a performance measurement tool.
KMS key rotation manages cryptographic keys and is not a performance measurement tool.
X-Ray traces requests across services and visualizes latency and error locations.
X-Ray traces requests across services and visualizes latency and error locations.
S3 Lifecycle manages objects and does not provide distributed tracing.
S3 Lifecycle manages objects and does not provide distributed tracing.
DNS records do not trace service-to-service processing.
DNS records do not trace service-to-service processing.
Check official documentation
Compare the following points with the official documentation.
AWS X-Rayのトレースとサービスマップの公式説明を確認する。
What to confirm
分散ワークロードの可視性をX-Rayへ対応付けられる。
Key points
- AWS X-Ray
- Distributed tracing
- Service map
Notes
- Environment: AWS公式X-Rayドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Cross-service visibility
A trace correlates timing across API Gateway, Lambda, and DynamoDB so the slow segment is visible.
Metrics versus traces
Metrics show aggregate behavior, while traces explain the path and timing of an individual request.