-
-
Notifications
You must be signed in to change notification settings - Fork 284
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
Add Amazon MQTT support #17
Comments
Can you provide more details on this issue? I've validated the client can connect to AWS IoT Core with X.509 certs. |
Client certificates now allow connecting to Amazon's IoT service but while testing it I experience disconnects due to missing permissions to subscribe with a wild card. |
I tested with broad permissions applied to my certificate which allows publishing and subscribing on any topic (a One note about using this client with AWS IoT Core is that broker does not permit subscribing to "$SYS" or any topic sub-space of "$SYS" such as "$SYS/#". The AWS IoT Core broker will disconnect clients trying to subscribe in this topic space. Because this is a default subscription in new connections from MQTT Explorer, it may yield a perception that this client and AWS IoT Core are incompatible. For future readers, drop the "$SYS/#" default subscription before connecting to AWS IoT Core. |
Thanks for sharing 👍. |
Close since it is working, documentation is missing. #194 |
Needs certificates, possibly a different mqtt lib.
(amazon examples ship with a working lib)
The text was updated successfully, but these errors were encountered: