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

[Feature request] Basic ingestion #60

Open
IK-Adrian opened this issue Jul 23, 2024 · 2 comments
Open

[Feature request] Basic ingestion #60

IK-Adrian opened this issue Jul 23, 2024 · 2 comments

Comments

@IK-Adrian
Copy link

Use the basic ingestion for the published messages that are not part of $aws/+.

@gregbreen
Copy link
Contributor

The awslabs topics have been modelled to use the accepted and rejected topic extensions, in the same way as most reserved topics. This wouldn't be possible if basic ingest was used.

The MQTT messaging costs associated with the awslabs/things/thingName/certificate/create and awslabs/things/thingName/certificate/commit topics are a tiny fraction of the overall cost of the solution.

@IK-Adrian
Copy link
Author

I understand the messaging cost reduction would be small, but it would also mean that those messages would only be delivered to IoT rules and no other device would be able to subscribe to those topics. I know this doesn't replace authorization but reducing the attack surface is always nice from a sybersecurity point of view.

Despite this, I understand this suggested change has a minor impact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants