* The code for passing the trace context to a sub process has been improved to increase code reuse. This code is used when the action templates are rendered in a sub process. * A macro has also been added for the error term that is thrown when the action shall be stopped after the templates has been rendered. This is also done to reduce code duplication and to reduce the risk of introducing bugs due to typos. * Fix incorrect type spec Thanks to @zmstone for suggesting these improvements in comments to a PR (https://github.com/emqx/emqx/pull/12916). |
||
|---|---|---|
| .. | ||
| priv/dynamo | ||
| src | ||
| test | ||
| BSL.txt | ||
| docker-ct | ||
| README.md | ||
| rebar.config | ||
EMQX DynamoDB Bridge
DynamoDB is a high-performance NoSQL database service provided by Amazon that's designed for scalability and low-latency access to structured data.
It's often used in applications that require fast and reliable access to data, such as mobile, ad tech, and IoT.
The application is used to connect EMQX and DynamoDB. User can create a rule and easily ingest IoT data into DynamoDB by leveraging EMQX Rules.
Documentation
-
Refer to Ingest data into DynamoDB for how to use EMQX dashboard to ingest IoT data into DynamoDB.
-
Refer to Rules engine for the EMQX rules engine introduction.
HTTP APIs
-
Several APIs are provided for bridge management, which includes create bridge, update bridge, get bridge, stop or restart bridge and list bridges etc.
Refer to API Docs - Bridges for more detailed information.
Contributing
Please see our contributing.md.
License
EMQ Business Source License 1.1, refer to LICENSE.