Support cannot stitch API Gateway access logs to Lambda log lines for one citizen complaint because nothing ties the records together. What should the app include?
Select an answer to reveal the explanation.
Short Explanation
Without a shared request id, API Gateway and Lambda logs are two novels with no chapter numbers. Stamp a correlation id across the path and support can follow one citizen end to end.
Full Explanation
Correlation or request identifiers propagated from API Gateway into Lambda (and downstream logs) let support filter one citizen journey across components. Removing identifiers, logging only account IDs, or using Cost Explorer cannot stitch per-request timelines needed for root-cause speed.