Skip to content

Make README.md more specific about which AWS Lambda images cause CA #720

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.

Sign up for GitHub

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

Merged
eamsden merged 2 commits into from
May 28, 2026
Merged

Make README.md more specific about which AWS Lambda images cause CA #720

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
225e6d6
Make README.md more specific about which AWS Lambda images cause CA
eamsden May 28, 2026
b5e837e
Header fix
eamsden May 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1265,9 +1265,9 @@ See the earlier part of this section for details on what environments are suppor

Some platforms are not loading the system CA list properly due to quirks with how the platforms work.

#### AWS Lambda .NET CA Loading Issues
#### AWS Lambda .NET 8 CA Loading Issues

Due to a [recent change](https://github.com/aws/aws-lambda-dotnet/pull/1661) in newer AWS .NET Lambda images to force
Due to a [change](https://github.com/aws/aws-lambda-dotnet/pull/1661) in AWS .NET 8 Lambda images to force
override the `SSL_CERT_FILE` environment variable, the CA list cannot be loaded from the system properly in our
Rust-based extension. This may cause errors like:

Expand Down
Loading