-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
connect bisquitt gateway to aws Iot core #69
Comments
@tra8080 I no longer work on Bisquitt as I’ve quit @energomonitor a while ago, but I had a quick look. According to the docs, AWS IoT Core broker is based on MQTT 3.1.1 or 5.0, which means Bisquitt should be able to connect to it. However, the broker’s implementation differs from these specifications a bit. The differences are documented, but I can’t tell how significant they are for Bisquitt. So I’m not 100% sure whether it will work with the broker or not. As for the connection itself, you need to point Bisquitt to the broker using environment variables or command-line options. Please refer to That’s it from my side. I guess @mprymek should be able to provide more information/help. |
AWS IoT Core authenticates MQTT clients by certificates by default and I don't thing there's any other option. Bisquitt supports username/password (SASL PLAIN) authentication only. So I'm afraid secure connection to AWS IoT Core is not possible at the moment. I'm by no means an expert in security protocol internals but maybe it could be possible to somehow "pass" the MQTT-SN connection DTLS client certificate to MQTT connection but this is not implemented in Bisquitt and is not planned for the near future neither. Anyways, connection to AWS IoT Core surely is a very relevant topic and I will investigate the possibilities. If you have any suggestions, feel free to contact me. |
thanks for the reply. |
@mprymek @dmajda
Is It possible to connect bisquitt gateway to aws Iot core mqtt broker?
If yes pls let me know how we can achieve that.
The text was updated successfully, but these errors were encountered: