platform · inferred from evidence
AWS Lambda
A serverless compute platform mentioned as the source of logs with runtime-specific formats.
- Stripe webhook signature mismatch on AWS Lambda: use raw event.body and the whsec_ secret
On AWS Lambda (via API Gateway), stripe.webhooks.constructEvent failed with No signatures found matching the expected signature for payload. API Gateway hands the Lambda a parsed JSON object as the body, and JSON.stringify-ing it back subtl
- Bolt WorkflowStep executes multiple times when deployed to Lambda / serverless
A Bolt WorkflowStep deployed to AWS Lambda (following Slack's bolt-js serverless deployment docs) has its `execute` function invoked multiple times per workflow run. In Socket Mode the same code worked perfectly. The duplicate invocations c
- Logz.io CloudWatch shipper misparses NodeJS Lambda logs (no log level)
The Logz.io CloudWatch logs shipper parses AWS Lambda log lines assuming a 3-part format (timestamp, requestID, message), but NodeJS Lambda logs have a 4-part format that includes the log level. On NodeJS functions the shipper misparses the
- Google Secret Manager Could not load the default credentials from AWS Lambda nodejs client
Creating secrets in GCP Secret Manager from an AWS Lambda using the Node.js client fails with: Error: Could not load the default credentials, even when projectId and the path to a service-account JSON key file are passed to the SecretManage