DevOps & CI/CD
Bug Report
Correlation ID in API logs but missing in SQS consumers: propagating it with Lambda Powertools
Our API Lambda logs carried a correlation_id from API Gateway, but the SQS consumer logs had none, so we could not follow a request across the queue. Powertools only reads correlation IDs from the event it is given. How we passed the ID as a message attribute and injected it per record in the consumer.