Because the Langchain Lambda Cloudwatch Log group was not automatically created, some churn was involved in sourcing logs for the lambda. Creating a CW log group manually in the AWS console with the expected name does work, but is not an ideal solve.
Because the Langchain Lambda Cloudwatch Log group was not automatically created, some churn was involved in sourcing logs for the lambda. Creating a CW log group manually in the AWS console with the expected name does work, but is not an ideal solve.