Is this is also the correct way of creating a client, according to version 1.11, uisng sdk c++, by giving NULL in endpoint ?

[Sach1nAgarwal]

typedef Aws::S3::S3Client S3Client_aws;

std::shared_ptr< Aws::S3::Endpoint::S3EndpointProviderBase > endpointProvider = Aws::MakeShared<Aws::S3::Endpoint::S3EndpointProvider>(NULL);

Aws::Auth::AWSCredentials credentials;
Aws::Client::ClientConfiguration clientConfig;
credentials.SetAWSAccessKeyId(Aws::String(access_key.c_str(), access_key.size()));
credentials.SetAWSSecretKey(Aws::String(secret_key.c_str(), secret_key.size()));
std::unique_ptr<S3Client_aws>(new S3Client_aws(credentials, endpointProvider, clientConfig));

[jmklix]

Is this working for you? If so then you can keep doing it this way.
The suggested way to provide credentials is via the default credentials file:

Default Credential Provider Chain

The default credential provider chain does the following:

1. Checks your environment variables for AWS Credentials
2. Checks your $HOME/.aws/credentials file for a profile and credentials
3. Contacts and logs in to a trusted identity provider (Cognito, Login with Amazon, Facebook, Google). The sdk looks for the login information to these providers either on the environment variables: AWS_ROLE_ARN, AWS_WEB_IDENTITY_TOKEN_FILE, AWS_ROLE_SESSION_NAME. Or on a profile in your $HOME/.aws/credentials.
4. Checks for an external method set as part of a profile on $HOME/.aws/config to generate or look up credentials that isn't directly supported by AWS.
5. Contacts the ECS TaskRoleCredentialsProvider service to request credentials if Environment variable AWS_CONTAINER_CREDENTIALS_RELATIVE_URI has been set.
6. Contacts the EC2MetadataInstanceProfileCredentialsProvider service to request credentials if AWS_EC2_METADATA_DISABLED is NOT set to ON.

The simplest way to communicate with AWS is to ensure we can find your credentials in one of these locations.

[Sach1nAgarwal]

Will endpointprovider as NULL will break anything ?

[jmklix]

Yes, it will break the client

[Sach1nAgarwal]

Is there any examples to create clients?
Or creating clients Using only credential?

[jmklix]

You can find a bunch of examples here for how to create clients

Aws::Client::ClientConfiguration clientConfig;
clientConfig.region = "us-east-1";
Aws::S3::S3Client client(clientConfig);
//more s3 code

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.

[parsley72]

I can't find any examples that explain how to use S3EndpointProviderBase, or any documentation for it. I've been using v1.9.379 (Nov 6, 2022) and this code worked fine:

            Aws::Client::ClientConfiguration clientConfig;
            clientConfig.region = s3_region_end_point.c_str();
            clientConfig.scheme = Aws::Http::Scheme::HTTPS;
            clientConfig.connectTimeoutMs = 2000;
            clientConfig.requestTimeoutMs = 3000;
            _pS3Client = new Aws::S3::S3Client(Aws::Auth::AWSCredentials(Aws::String(s3_access_key.c_str()),
                    Aws::String(s3_secret_access_key.c_str())),
                    clientConfig);

I just upgraded to 1.11.404 (Sep 13, 2024) and the build breaks because I now need an S3EndpointProviderBase. @jmklix says setting it as NULL will break the client, so what do I set it to?

[jmklix]

@parsley72 are you trying to use a different endpoint? or are you just trying to fix an error?

As noted in the docs here:

The type for the S3 Client Endpoint Provider. Inherit from this Base class / "Interface" should you want to provide a custom endpoint provider. The SDK must use service-specific type for each service per specification.

This means that you need to set it to the correct custom endpoint provider. But I'm not sure if that is what you want. If you just want to get it working please let us know what error you are getting. (Also opening a new discussion is preferred rather than commenting on an already answered one)

[parsley72]

I'm trying to fix the build - as I said, the code that worked fine for v1.9.379 doesn't work with v1.11.404 because the constructor requires an endpoint parameter. Setting it to nullptr seems to work fine but you said "it will break the client". So what should I be doing?

[SergeyRyabinin]

I'm trying to fix the build - as I said, the code that worked fine for v1.9.379 doesn't work with v1.11.404 because the constructor requires an endpoint parameter. Setting it to nullptr seems to work fine but you said "it will break the client". So what should I be doing?

Hi @parsley72 ,

Setting the endpoint provider to nullptr is fine, the client will use the default standard endpoint computation in such case.
You might want to provide a custom implementation if you need to customize the behavior.

Best regards,
Sergey