Fix S3 backup TLS failures with custom CA certificates for CRT-based clients #507
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bfeshti
approved these changes
Dec 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Neo4j's native cloud storage backup uses AWS CRT-based S3 clients (AwsCrtAsyncHttpClient) which:
javax.net.ssl.trustStore)s3SkipVerify: truesettingTo solve the issue:
Extended
importCustomCA()to update system CA certificates in addition to JKS truststore:/usr/local/share/ca-certificates/custom-s3-ca.crtupdate-ca-certificatesto refresh OS trust storeChanges are fully backward compatible - only activates when
s3CASecretNameis configured