unnamazon wrote on June 18, 2018:
I have configured, registered a thing, attached a certificate and a policy to it. Then, using Amazon FreeRTOS or using a MQTT broker client - MQTT.FX, when I try to connect to AWS IOT, I am refused connection from the server. Whereas with openssl (8443) or telnet(443) to the same endpoint address and certificates is working.
I am an IAM user for a certain AWS account and my policies are also attached. I have tried disabling the firewall too. Is this anything to do with certain policies not available for my IAM user?
Log from Amazon freertos:
MQTT echo attempting to connect to XXXXXX.iot.us-east-2.amazonaws.com.
Sending command to MQTT task.
Received message 10000 from queue.
eMQTTConnectRequest
[AT]: AT+CIPDOMAIN=“XXXXXX.iot.us-east-2.amazonaws.com”
Can’t get remote IP
[AT]: AT+TLSCLOSE=0
[AT]: AT+TLSCONN=0,“TCP”,“XXXXXX.iot.us-east-2.amazonaws.com”,8883
Resp: AT+TLSCLOSE=0
Socket not init
ERROR
Failed to connect to :8883 at_ret -2
prvSetupConnection About to close socket.
No data to received -1
[AT]: AT+TLSCLOSE=0
Socket closed.
I have also attached the connection profile in MQTT.fx client