Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

AWS_IO_TLS_ERROR_NEGOTIATION_FAILURE on 1.0.6 (awscrt 0.5.13)

See original GitHub issue

I’ve searched for previous similar issues and didn’t find any solution

Describe the bug After upgrading my installation to awsiotsdk-1.0.6 it stopped working with awscrt failing to authorize with aws’ backend. Might be connected with awscrt upgrade to 0.5.13.

SDK version number awsiotsdk-1.0.6

Platform/OS/Device rpi3b+

To Reproduce (observed behavior) Upgrade awsiotsdk to version 1.0.6.

Expected behavior Should work as expected.

Logs/output

Apr 15 06:55:01 raspberrypi python3[581]: Connecting to something-east-1.amazonaws.com with client ID 'foo-bar-baz'...
Apr 15 06:55:01 raspberrypi python3[581]: Traceback (most recent call last):
Apr 15 06:55:01 raspberrypi python3[581]:   File "app.py", line 86, in <module>
Apr 15 06:55:01 raspberrypi python3[581]:     connect_future.result()
Apr 15 06:55:01 raspberrypi python3[581]:   File "/usr/lib/python3.7/concurrent/futures/_base.py", line 432, in result
Apr 15 06:55:01 raspberrypi python3[581]:     return self.__get_result()
Apr 15 06:55:01 raspberrypi python3[581]:   File "/usr/lib/python3.7/concurrent/futures/_base.py", line 384, in __get_result
Apr 15 06:55:01 raspberrypi python3[581]:     raise self._exception
Apr 15 06:55:01 raspberrypi python3[581]: awscrt.exceptions.AwsCrtError: AwsCrtError(name='AWS_IO_TLS_ERROR_NEGOTIATION_FAILURE', message='TLS (SSL) negotiation failed', code=1029)
Apr 15 06:55:01 raspberrypi systemd[1]: app.service: Main process exited, code=exited, status=1/FAILURE

Issue Analytics

State:
Created 3 years ago
Comments:17 (6 by maintainers)

Top GitHub Comments

13reactions

adolfogccommented, Apr 27, 2020

@JonathanHenson I was using the old endpoint (<endpoint-id>.iot.us-east-1.amazonaws.com), I switched to the ATS one (<endpoint-id>-ats.iot.us-east-1.amazonaws.com) and now it works. Thanks for your help!

5reactions

DavidOgunsAWScommented, May 6, 2020

Thank you Mario for sharing the link to that post here. Again: https://aws.amazon.com/blogs/iot/aws-iot-core-ats-endpoints/

The default configuration for V2 device SDKs will no longer work with the old non-ATS endpoints. Run aws --region <region> iot describe-endpoint --endpoint-type "iot:Data-ATS" to get the ATS endpoint.

Top Results From Across the Web

AWSCRT (AWS IoT) TLS Negotiation timeout Python

It works well using WiFi on my Raspbian device. When using a GSM module I receive below error after ~5-6s: 'aws.crt.exceptions.AwsCrtError: ...

Troubleshooting client devices - AWS IoT Greengrass

Use the following information to troubleshoot issues with Greengrass discovery in the AWS IoT Device SDK v2 for Python . Topics. awscrt.exceptions.AwsCrtError: ...

conda-forge - :: Anaconda.org

asciietch, 1.0.6, BSD-2-Clause, X, A library for graphing charts using ascii ... aws-error-utils, 2.6.0, Apache-2.0, X, Error-handling functions for boto3/ ...

awsiot.mqtt_connection_builder — AWS IoT Device SDK v2 ...

The function should take the following arguments return nothing: connection ( awscrt.mqtt.Connection ): This MQTT Connection. error ( ...