Skip to content

awscli >= 1.11.108 fails to resolve DNS name for DNS-compatible buckets #2697

@tuukkamustonen

Description

@tuukkamustonen

With something like:

aws --debug s3 cp s3://some_bucket/file.zip .

With awscli-1.11.108 + botocore-1.5.71, it hangs to:

2017-07-05 13:47:11,464 - MainThread - botocore.vendored.requests.packages.urllib3.connectionpool - INFO - Starting new HTTPS connection (1): s3.amazonaws.com

With awscli-1.11.107 + botocore-1.5.70, it succeeds because:

2017-07-05 13:48:17,209 - MainThread - botocore.vendored.requests.packages.urllib3.connectionpool - INFO - Starting new HTTPS connection (1): some_bucket.s3.amazonaws.com

1.11.107 also has this:

2017-07-05 13:48:17,208 - MainThread - botocore.utils - DEBUG - Checking for DNS compatible bucket for: https://s3.amazonaws.com/some_bucket/file.zip
2017-07-05 13:48:17,208 - MainThread - botocore.utils - DEBUG - URI updated to: https://some_bucket.s3.amazonaws.com/file.zip

But these logging lines are missing in 1.11.108.

Metadata

Metadata

Labels

investigatingThis issue is being investigated and/or work is in progress to resolve the issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions