Problem with AWS and ESH5 | Thales IoT Developer Community
July 31, 2017 - 6:11pm, 6899 views
Hello, I hope you can help me, I am trying to connect an ESH5 to AWS IOT, but using MQTT with SSL has been impossible, I have done the following:
a) I configured AWS oit (All steps according to manual) and then download the following security files:
- 63daef3df8-certificate.pem.crt,
- 63daef3df8-private.pem.key,
- 63daef3df8-public.pem.key
b) Then download the Root CA from Symantec Site (File pem, which I called RootCA.pem and after I converted it to .DER), finally I used the MQTT.FX tool to test and everything works correctly.
c) After a Make the Midlet App Using Paho from Gemalto Code, it compiled without problems.
d) Then, I make the netxs steps(IoT-AuterEjemplo is my app):
java -jar jseccmd.jar -cmd AddHttpsCertificateUntrusted -filename RootCA.der > AddHttpsCertificateUntrusted.bin
java -jar jseccmd.jar -cmd AddHttpsClientCertificateUntrusted -filename 63daef3df8-certificate.pem.crt -keyfilename 63daef3df8-private.pem.key > AddHttpsClientCertificateUntrusted.bin
at^sjmsec="cmd",0B00310001000500020001
at^sjmsec?
^SJMSEC: 1,1,1,1
at^sjmsec="file",AddHttpsCertificateUntrusted.bin
at^sjmsec="file",AddHttpsClientCertificateUntrusted.bin
AT^SJAM=0,"a:/IoT-AuterEjemplo.jad",""
AT^SJAM=1,"a:/IoT-AuterEjemplo.jad",""
But when I run and try to connect with AWS appear the next error
[MainMidlet]: Connecting to broker: ssl://a1h7rt21wt5j74.iot.us-east-1.amazonaws.com:8883
[MainMidlet]: MqttException system error:
reason 32103
msg Unable to connect to server
loc Unable to connect to server
cause java.io.IOException: -213 SSL-Error: revcd alert fatal error
excep Unable to connect to server (32103) - java.io.IOException: -213 SSL-Error: revcd alert fatal error
But when I try to connect with tcp://iot.eclipse.org:1883 works very good!!
My firmware is
Cinterion
EHS6
REVISION 03.001
A-REVISION 00.000.14
Hello,
You should update the module's firmware to the latest version REVISION 03.001 A-REVISION 00.000.51. The version that you are using does not support the connection to AWS yet. The newer version contains updated ssl libraries and should be working with AWS.
Regards,
Bartłomiej
Thanks for you response, but where i can get the last version of firmware ?
Hello,
Generally you should be able to get all the documentation and software from your local Gemalto hardware supplier.
I've sent you an email - please check.
Regards,
Bartłomiej
Hi, i charged the new firmware but the problem continued , the error was:
Connection lost (31209) - java.io.EOFException
But the solution is change one line of code:
qos =2
by
qos= 0
and the program works!!!!!!
the question is whats means qos on MqTT protocol?
You can find details e.g. here:
http://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-servic...
thank you!!!
AuthFailure is the error that is disturbing me trying to connect an ESH5 to AWS IOT. Earlier I was facing similar kind of issue and got cleared after going through this blog. But., later when I executed, AuthFailure is the new one where I got struck.
Env: MacOsX 10.10.2
Ruby: 2.1.5
Vagrant: 1.7.2
vagrant-aws: 0.6.0
vagrant up --provider=aws
An unexpected error occurred when executing the action on the
<my machine> machine. Please report this as a bug:
AuthFailure => AWS was not able to validate the provided access credentials
Do you have a good time on your device?
Best regards,
Michał