racheliurui
commented
4 years ago Just found the issue with setting the endpoint, modified the https://github.com/aws-samples/aws-iot-events-accelerators/blob/2905825720d9dd252d8d1878f5b363a60b87d054/integratingmachinelearning/docker/simulated_motor.py#L27
The endpoint here should be the thing's endpoint not static data.iot.[region].amazon.aws.com. For me it's something like
xxxxxxxxx-ats.iot.us-east-1.amazonaws.comBut after that, still I get SSL certificate error,
aws-iotevents-iml-simulatedmotor | Endpoint :a2rizlo4ii9h59-ats.iot.us-east-1.amazonaws.com
aws-iotevents-iml-simulatedmotor | mqttc.connect()
aws-iotevents-iml-simulatedmotor | File "/usr/local/lib/python2.7/site-packages/AWSIoTPythonSDK/MQTTLib.py", line 513, in connect
aws-iotevents-iml-simulatedmotor | return self._mqtt_core.connect(keepAliveIntervalSecond)
aws-iotevents-iml-simulatedmotor | File "/usr/local/lib/python2.7/site-packages/AWSIoTPythonSDK/core/protocol/mqtt_core.py", line 196, in connect
aws-iotevents-iml-simulatedmotor | self.connect_async(keep_alive_sec, self._create_blocking_ack_callback(event))
aws-iotevents-iml-simulatedmotor | File "/usr/local/lib/python2.7/site-packages/AWSIoTPythonSDK/core/protocol/mqtt_core.py", line 223, in connect_async
aws-iotevents-iml-simulatedmotor | raise e
aws-iotevents-iml-simulatedmotor | ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:727)
In summary, 2 places need to be modified to make the sample work, 1) the MQTT endpoint should be the thing's endpoint, not just static region name. 2) the rootCA.pem should curl from the official website, not using the hard coded one from the cert folder.
============ I am trying to run through the sample, I haven changed region to us-east-1
1) certificate for the thing has been created and copied to certs folder under docker before run docker command 2) after cfn creation I can see the thing is created successfully with full access to publish message. 3) no firewall for outbound 8883 from the mac
The Cloudside configuration all works for me, but the client simulation docker image gave me exception as below,