- Newest
- Most votes
- Most comments
The AWS Rust SDK allows disabling SSL verification by using the rustls library. This involves creating a custom struct that implements the ServerCertVerifier trait, where the verify_server_cert function always returns Ok(). Then, you configure the S3 client to use this verifier. The detailed code is available in this GitHub discussion.
https://github.com/awslabs/aws-sdk-rust/discussions/650
If you're using the boto3 library, disabling SSL verification is as simple as passing verify=False when creating your S3 client: https://stackoverflow.com/questions/60664637/sslerror-using-boto https://github.com/iterative/dvc/issues/1394
s3 = boto3.client('s3', verify=False)
In the AWS SDK for Java, you can disable SSL verification by setting the TRUST_ALL_CERTIFICATES configuration option to true. https://stackoverflow.com/questions/54749971/is-it-possible-to-disable-ssl-certificate-checking-in-the-amazon-kinesis-consume
final AttributeMap attributeMap = AttributeMap.builder()
.put(SdkHttpConfigurationOption.TRUST_ALL_CERTIFICATES, true)
.build();
final SdkHttpClient sdkHttpClient = new DefaultSdkHttpClientBuilder().buildWithDefaults(attributeMap);
return S3Client.builder()
.httpClient(sdkHttpClient)
.build();
Relevant content
- asked 2 months ago
- asked 6 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 21 days ago
Hello Salman, thank you so much for taking time to read the question and giving answer with code samples. I really appreciated that. However, the question and the problem we are addressing here is different. The devices are in the field, so if we will need to send any updates to the devices, we have to do OTA and that is not working right now because when the OTA process is initiated, the S3 bucket rejects the request because the certificate stored in the device's memory is not supported and identified by AWS anymore. Can you please suggest a way to bypass SSL authentication from AWS?