http-connection static: Client connection failed with error 1049 (AWS_IO_SOCKET_NO_ROUTE_TO_HOST)

[oleg-boulanov]

Describe the bug

Aws::SDKOptions sdkOptions;
Aws::InitAPI(sdkOptions);
Aws::Client::ClientConfiguration cfg;
cfg.region = "us-east-1";
auto client = Aws::MakeShared<BedrockRuntimeClient>("nova", cfg);

This code produces tons of errors like:

[ERROR] 2025-10-03 19:13:59.234 socket [28548] id=013E7B88 handle=000002F4: connect completion triggered with error -1073741252
[ERROR] 2025-10-03 19:13:59.234 channel-bootstrap [28548] id=013B3BD8: Connection failed with error_code 1049 : AWS_IO_SOCKET_NO_ROUTE_TO_HOST.
[ERROR] 2025-10-03 19:13:59.234 http-connection [28548] static: Client connection failed with error 1049 (AWS_IO_SOCKET_NO_ROUTE_TO_HOST).
[ERROR] 2025-10-03 19:13:59.234 CRTHttpClient [28548] Obtaining connection failed because aws-c-io: AWS_IO_SOCKET_NO_ROUTE_TO_HOST, socket connect failure, no route to host.
[ERROR] 2025-10-03 19:13:59.234 EC2MetadataClient [50580] Http request to retrieve credentials failed
[ERROR] 2025-10-03 19:13:59.349 socket [84560] id=013E7CB8 handle=00000300: connect completion triggered with error -1073741252
[ERROR] 2025-10-03 19:13:59.349 channel-bootstrap [84560] id=013B3BD8: Connection failed with error_code 1049 : AWS_IO_SOCKET_NO_ROUTE_TO_HOST.
[ERROR] 2025-10-03 19:13:59.349 http-connection [84560] static: Client connection failed with error 1049 (AWS_IO_SOCKET_NO_ROUTE_TO_HOST).
[ERROR] 2025-10-03 19:13:59.349 CRTHttpClient [84560] Obtaining connection failed because aws-c-io: AWS_IO_SOCKET_NO_ROUTE_TO_HOST, socket connect failure, no route to host.
[ERROR] 2025-10-03 19:13:59.350 EC2MetadataClient [50580] Http request to retrieve credentials failed
[ERROR] 2025-10-03 19:13:59.350 EC2MetadataClient [50580] Can not retrieve resource from http://169.254.169.254/latest/api/token
[ERROR] 2025-10-03 19:13:59.460 socket [80180] id=013E9158 handle=00000300: connect completion triggered with error -1073741252
[ERROR] 2025-10-03 19:13:59.460 channel-bootstrap [80180] id=013B3BD8: Connection failed with error_code 1049 : AWS_IO_SOCKET_NO_ROUTE_TO_HOST.
[ERROR] 2025-10-03 19:13:59.460 http-connection [80180] static: Client connection failed with error 1049 (AWS_IO_SOCKET_NO_ROUTE_TO_HOST).
[ERROR] 2025-10-03 19:13:59.460 CRTHttpClient [80180] Obtaining connection failed because aws-c-io: AWS_IO_SOCKET_NO_ROUTE_TO_HOST, socket connect failure, no route to host.
...
[ERROR] 2025-10-03 19:14:00.228 CRTHttpClient [86048] Obtaining connection failed because aws-c-io: AWS_IO_SOCKET_NO_ROUTE_TO_HOST, socket connect failure, no route to host.
[ERROR] 2025-10-03 19:14:00.228 EC2MetadataClient [50580] Http request to retrieve credentials failed
[ERROR] 2025-10-03 19:14:00.228 EC2MetadataClient [50580] Can not retrieve resource from http://169.254.169.254/latest/meta-data/placement/availability-zone

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

No error messages, maybe info or warnings, at the most?
Is there a way to configure SDK not to attempt those calls?

Current Behavior

Tons of error messages in the log

Reproduction Steps

Aws::SDKOptions sdkOptions;
sdkOptions.loggingOptions.logLevel = Aws::Utils::Logging::LogLevel::Error;

Possible Solution

No response

Additional Information/Context

No response

AWS CPP SDK version used

1.11.661

Compiler and Version used

Visual Studio 2022

Operating System and version

Windows 11

[pulimsr]

Thank you for reporting this issue. Based on the error logs, this is just a network connectivity problem rather than an SDK bug. The AWS_IO_SOCKET_NO_ROUTE_TO_HOST errors indicate your system cannot reach AWS endpoints.

I've tested the same code structure and it works successfully:

#include <aws/core/Aws.h>
#include <aws/bedrock-runtime/BedrockRuntimeClient.h>

int main() {
    Aws::SDKOptions sdkOptions;
    Aws::InitAPI(sdkOptions);
    
    Aws::Client::ClientConfiguration cfg;
    cfg.region = "us-east-1";
    auto client = Aws::MakeShared<Aws::BedrockRuntime::BedrockRuntimeClient>("nova", cfg);
    
    // Test API call
    Aws::BedrockRuntime::Model::ListAsyncInvokesRequest request;
    auto outcome = client->ListAsyncInvokes(request);
    
    Aws::ShutdownAPI(sdkOptions);
    return 0;
}

Please check your network connectivity, firewall settings, and try using AWS CLI to confirm if you can reach AWS services.

[oleg-boulanov]

Thank you for reply.

But please note that the "errors" in the log are not about service endpoints, but rather about http://169.254.169.254/ which is an EC2 instance, while I'm running it on a standalone laptop.

My point is that these are actually no errors, just polluting the logs.

[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.

[sbiscigl]

My point is that these are actually no errors, just polluting the logs.

The IMDS EC2 credentials provider is part of the default credentails provider chain, specifically called the IMDS provider.

per the documentation you can disable this in several different ways. (our code)

ec2_metadata_v1_disabled - shared AWS config file setting
AWS_EC2_METADATA_V1_DISABLED - environment variable

additionally we support a additionally constructor for client configuration not call IMDS for region.

[oleg-boulanov]

additionally we support a additionally constructor for client configuration not call IMDS for region.

Thank you, @sbiscigl ! That was the missing part.