aws-sdk-cpp-1.11.323 curlcode：35 SSL connect error

[txh1873749380]

Describe the bug

In the aws-sdk-cpp-1.11.323 version, curlcode: 35 ssl connect error occurred while verifying a small demo, and verifySSL was disabled.
Here is the demo code:

Expected Behavior

It is expected that the execution will be successful and the size will be calculated as follows:

Current Behavior

Reproduction Steps

Possible Solution

No response

Additional Information/Context

demo g++ compilation command:

AWS CPP SDK version used

aws-sdk-cpp-1.11.323

Compiler and Version used

g++ 8.3.1

Operating System and version

Kernel :linux Kernel version:5.14.21 x86_64 centos7

[jmklix]

How are you building this sdk? and can you paste your code snippets in code block rather then in screenshots?

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.

[txh1873749380]

How are you building this sdk? and can you paste your code snippets in code block rather then in screenshots?

This error occurred when I was accessing minio's bucket in this demo：

#include <iostream>
#include <fstream>
#include <aws/s3/S3Client.h>
#include <aws/core/Aws.h>
#include <aws/core/auth/AWSCredentialsProvider.h>
#include <aws/transfer/TransferManager.h>
#include <aws/s3/model/HeadObjectRequest.h>
#include <aws/s3/model/HeadBucketRequest.h>


#include<sys/types.h> 
#include<sys/stat.h>
#include<fcntl.h>

static const char* const ALLOCATION_TAG = "S3_HEADOBJECT";


int main(int argc, char* argv[]) {
  Aws::SDKOptions options;
  Aws::InitAPI(options);
  {
    // S3 End Point
    const Aws::String endPoint = "172.16.10.115:9000";
    const Aws::String bucketName = "hcc-bucket";
    //const Aws::String objectName = "project_id_1";
    const Aws::String objectName = argv[1];
    const Aws::String region = "us-west-2";
    // 
    const Aws::String accessKey = "minioadmin";
    const Aws::String secretKey = "minioadmin";
    bool using_virtual_address = false;


    // S3 Client
    Aws::Client::ClientConfiguration config;
    config.verifySSL = false;
    config.scheme = Aws::Http::Scheme::HTTP;
    config.region = region;

    //bool using_virtual_address = bucket_cfg.s3_uri_style == 0 ? true : false;
    Aws::Auth::AWSCredentials cred(accessKey, secretKey);

    auto s3Client = Aws::MakeShared<Aws::S3::S3Client>(
                 ALLOCATION_TAG,
                 cred,
                 config,
                 Aws::Client::AWSAuthV4Signer::PayloadSigningPolicy::Never,
                 using_virtual_address);
    s3Client->OverrideEndpoint(endPoint);

    // aws request
    Aws::S3::Model::HeadObjectRequest aws_req;
    aws_req.SetBucket(bucketName);
    aws_req.SetKey(objectName);

    Aws::S3::Model::HeadObjectOutcome aws_resp = s3Client->HeadObject(aws_req);
    if (aws_resp.IsSuccess()) {
        long long size_total = aws_resp.GetResult().GetContentLength();
        std::cout << "objectName:" << objectName << ", size:" << size_total << std::endl;
    } else {
        // has error
        auto err = aws_resp.GetError();
        std::cout << "head object error, objectName:"<< objectName << ", errno:" << (int)err.GetErrorType() << ", errmsg:" << err.GetMessage()<< std::endl;
    }
  }

  Aws::ShutdownAPI(options);
  return 0;
}

[jmklix]

Can you reproduce this error when using AWS s3 buckets? We can't guarantee that this sdk will work with third party buckets (i.e. minio). If you can reproduce this with an s3 bucket then we can take a closer look.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.

[txh1873749380]

Can you reproduce this error when using AWS s3 buckets? We can't guarantee that this sdk will work with third party buckets (i.e. minio). If you can reproduce this with an s3 bucket then we can take a closer look.

Okay, I'll give it a try

[txh1873749380]

Can you reproduce this error when using AWS s3 buckets? We can't guarantee that this sdk will work with third party buckets (i.e. minio). If you can reproduce this with an s3 bucket then we can take a closer look.

Okay, I'll give it a try

在使用AWS s3 bucket时，是否可以重现此错误？我们不能保证这个sdk将与第三方bucket（即minio）一起工作。如果你能用一个s3桶来复制这个，那么我们就可以仔细看看了。

好吧，我试试

After our discussion, we want to support third-party bucket like ceph and minio. Do you have any other solutions to solve this problem?

[jmklix]

This sdk doesn't officially support and third-party buckets like ceph and minio. If they do work with this sdk, that is great. But we only guarantee compatibility with AWS s3 buckets. If the root cause is because of an issue with a third-party bucket, then you would need to contact the third-party bucket to see if they would fix the problem. The other possibility is that this is a problem with this sdk. To show that we need to be able to reproduce the same error (curlcode：35 SSL connect error) while using an AWS s3 bucket.

You can also use the respective sdk's for third-party buckets if you're using third-party buckets. This might be your best solution if you want to use ceph and minio.

[txh1873749380]

This sdk doesn't officially support and third-party buckets like ceph and minio. If they do work with this sdk, that is great. But we only guarantee compatibility with AWS s3 buckets. If the root cause is because of an issue with a third-party bucket, then you would need to contact the third-party bucket to see if they would fix the problem. The other possibility is that this is a problem with this sdk. To show that we need to be able to reproduce the same error (curlcode：35 SSL connect error) while using an AWS s3 bucket.

You can also use the respective sdk's for third-party buckets if you're using third-party buckets. This might be your best solution if you want to use ceph and minio.

该sdk不正式支持ceph和minio等第三方桶。如果他们确实使用这个SDK，那就太好了。但我们仅保证与AWS s3桶的兼容性。如果根本原因是第三方存储桶的问题，那么您需要联系第三方存储桶，看看他们是否会解决该问题。另一种可能是这个sdk有问题。为了说明我们需要能够在使用AWS s3存储桶时重现相同的错误（curlcode：35 SSL connect error）。

如果你使用的是第三方bucket，你也可以使用第三方bucket的相应sdk。如果你想使用ceph和minio，这可能是你最好的解决方案。

This sdk doesn't officially support and third-party buckets like ceph and minio. If they do work with this sdk, that is great. But we only guarantee compatibility with AWS s3 buckets. If the root cause is because of an issue with a third-party bucket, then you would need to contact the third-party bucket to see if they would fix the problem. The other possibility is that this is a problem with this sdk. To show that we need to be able to reproduce the same error (curlcode：35 SSL connect error) while using an AWS s3 bucket.

You can also use the respective sdk's for third-party buckets if you're using third-party buckets. This might be your best solution if you want to use ceph and minio.

According to our testing of aws bucket, we can get the expected effect, but we still hope to get the support of a third-party bucket, and I wonder whether your company will make compatibility requirements in the future.

[jmklix]

Sorry, but we don't plan to support third-party buckets at any point in the future. Closing this issue

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.