Skip to content
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

Closed
thomasnordquist opened this issue Jan 15, 2019 · 5 comments
Closed

Add Amazon MQTT support #17

thomasnordquist opened this issue Jan 15, 2019 · 5 comments
Labels
enhancement New feature or request
Projects

Comments

@thomasnordquist
Copy link
Owner

Needs certificates, possibly a different mqtt lib.
(amazon examples ship with a working lib)

@TheRyanBurke
Copy link

Can you provide more details on this issue? I've validated the client can connect to AWS IoT Core with X.509 certs.

@thomasnordquist
Copy link
Owner Author

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 don't have enough experience with Amazon's IoT platform to confirm it really works.
What is your experience so far?

@TheRyanBurke
Copy link

I tested with broad permissions applied to my certificate which allows publishing and subscribing on any topic (a "Resource": "*" policy in AWS terminology). This enabled me to connect and test pub/sub functionality with the client and another web client hosted in the AWS management console. There's a distinction in AWS policy definition between "subscribe to any topic" (a resource like "arn:aws:iot:REGION:ACCOUNT:topicfilter/*") and "subscribe to the MQTT wildcard topic" (a resource like "arn:aws:iot:REGION:ACCOUNT:topicfilter/#").

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.

@thomasnordquist
Copy link
Owner Author

thomasnordquist commented Jul 24, 2019

Thanks for sharing 👍.
I just might write a small introduction for it on https://mqtt-explorer.com next week.

@thomasnordquist
Copy link
Owner Author

Close since it is working, documentation is missing. #194

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Awesomize
Awaiting triage
Development

No branches or pull requests

2 participants