Attempting to possibly retrofit an existing AWS IoT platform to use Helium. Our end devices publish to specific topics for different scenarios however I do not see that possibility.
For example the way it works now is an end device specifies the topic and payload for a message to be published. The topic does match a pattern abc/123//abc/
The custom part could include a request Id that the end device is acknowledging. Is this functionality available or must I create a Lambda router to parse every message, determine the final topic destination, and then forward?