- Newest
- Most votes
- Most comments
Hi. In general, if AWS IoT Rules Engine doesn't have an action to route data to a particular service, Lambda would be a way to achieve it.
AWS IoT Core -> Rule -> Lambda -> DocumentDB
If you had a high rate of messages coming through, you could consider to insert something like SQS or KDS between the Rule and the Lambda, so the Lambda does batch processing of messages. This would help lower costs.
These would be amongst the simplest patterns to achieve what you want.
Hi there
From the note, I understand you want to connect my documentDB to an AWS IoT Core properly and you need it to be highly scalable to handle millions of devices. Please correct me if my understand is wrong.
Please note you would have to configure the IoT devices with a MongoDB client and use the SDK to insert data to DocumentDB but this is an out of scope solution for Support and would require your developers to build it.
I hope the above information is helpful.
References: 1.https://docs.aws.amazon.com/documentdb/latest/developerguide/documentdb-development.html 2.https://docs.aws.amazon.com/iot/latest/developerguide/iot-ddb-rule.html
Relevant content
- asked a year ago
- Accepted Answerasked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 5 months ago
Thanks for your response, you have fully understood my question.