-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Concurrent SES and DynamoDB use in Lambda causes Fatal error: Tls Context failed to create.
#1077
Comments
Thanks for your report. We'll investigate, and we'll get back to you if we need more info or resolve the problem. |
Error is thrown in |
Being tracked in CRT awslabs/aws-crt-swift#197 |
We've added a way to change log levels for CRT (one of our dependency which is where the error is being thrown from) as part of 0.35.0 release of aws-sdk-swift. We need trace level logs to determine what the specific issue is. Could you call this method once at application start to set the CRT log level to Please delete / censor out any personal information like credentials, etc. from the logs before posting. |
Closing this ticket as it has seen no customer interaction and has gone stale. |
Describe the bug
Attempting to send an email using
AWSSES
and put an item withAWSDynamoDB
concurrently in an AWS Lambda causes a crash fromFatal error: Tls Context failed to create.
Expected Behavior
The SDK does not crash
Current Behavior
The SDK crashes with the following message from the Lambda's CloudWatch logs:
Reproduction Steps
I have a full example with a SAM template at https://github.com/mgacy/aws-sdk-crash; the function code is:
Possible Solution
N/A
Additional Information/Context
The function is using runtime version:
provided:al2.v20
AWS SWIFT SDK version used
0.22.0
Compiler and Version used
Swift 5.7
Operating System and version
Built for
arm64
using theswift:5.7-amazonlinux2
imageThe text was updated successfully, but these errors were encountered: