ImportError: cannot import name 'PROTOCOL_TLS' from 'urllib3.util.ssl_' (*****/urllib3/util/ssl_.py)

[kishorekumarhanbar]

Describe the bug

Hi,

I am trying to use "import boto3" in my python code base, I am getting the following error and I am not sure why I am facing this issue.

ImportError: cannot import name 'PROTOCOL_TLS' from 'urllib3.util.ssl_' (*****/urllib3/util/ssl_.py)

I have verified version of boto3 and botocore and urlib3 i.e.
boto3 1.28.20
botocore 1.31.20
urllib3 1.26.16

pipdeptree --reverse | grep "requires: urllib3"
├── botocore==1.31.20 [requires: urllib3>=1.25.4,<1.27]
└── requests==2.31.0 [requires: urllib3>=1.21.1,<3]

I verified by going to ssl.py file I don't see any reference of 'PROTOCOL_TLS', can someone help me in resolving this issue and why I am seeing this.

Thanks

Expected Behavior

Should use the package already installed, the version of urllib3 is more than 1.24 so it should not have any problem also the latest urllib3 version is 2.0* but its not compatible with boto3

Current Behavior

its erroring out.

Reproduction Steps

upgraded boto3 botocore and urllib3

Possible Solution

No response

Additional Information/Context

No response

SDK version used

boto3 - 1.28.20

Environment details (OS name and version, etc.)

local env, boto3 -1.28.20 botocore - 1.31.20 urllib3 - 1.26.16

[tim-finnigan]

Hi @kishorekumarhanbar thanks for reaching out. The feature request for supporting urllib3 is being tracked here: boto/botocore#2926.

But the error you're reporting here has come up before, please refer to this comment for guidance: boto/botocore#2580 (comment)

PROTOCOL_TLS has been present in each release of urllib3 for the last ~3 years since 1.25.0. You can find the import workflow here. I'd double check the version of urllib3 you're using with botocore is actually 1.26.7. You can use urllib3.__version__ in your script to verify.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. 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 upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.