Device catalogue with IoT conformant devices. https://devices.amazonaws.com/search?page=1

Subscribing to topic

https://iot4beginners.com/tutorial-on-aws-iot-core-with-raspberry-pi-to-visualize-sensor-data/

In order not to define a rule for each single Thing - use wildcards.

• Example setup https://docs.aws.amazon.com/iot-sitewise/latest/userguide/ingest-data-from-iot-things.html
• Topic wildCards https://docs.aws.amazon.com/iot/latest/developerguide/topics.html#topicfilters
• Functions https://docs.aws.amazon.com/iot/latest/developerguide/iot-sql-functions.html

The MQTT topics for things in Iot Core are as structured as following:

$aws/things/alf-dev-con1-pi0-simulated/shadow/update/accepted
$aws/things/alf-dev-con1-pi1/shadow/update/accepted

Which match all things, independent of thing-name

SELECT * FROM '$aws/things/+/shadow/update/accepted'

Add the name of the topic - to the property “aliases” . So that you can use the topics - in the asset aliases.

Using ${topic(3)} which match the topic of the thing. The rules would redirect data to assets - depending on topic.