2 Answers
- Newest
- Most votes
- Most comments
2
Hi. Unfortunately I can't give you a timeline, other than to say this enhancement is not imminent. So it's necessary to continue using a Lambda for the time being.
0
Hello, I am product manager for AWS IoT Rules Engine. We do not have multi-measure support for Timestream Action in our immediate timeline. We can consider prioritizing the feature in our future roadmap based on customer requests. Kindly provide more info about your customer use case at aviu@amazon.com
answered a year ago
Relevant content
- asked 3 years ago
- asked 3 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Hi! Is there now any plan to make this a feature? We're making heavy use of lambda to support a similar case. Thanks!
Hello! We have been using the iotcore action, populating our tables with single-measure register for about a year. It seems that our costs related to queries and storage size could be fairly reduced by using multi-measure registers. Is it still not possible to give a timeline for this enhancement? Knowing that can help us decide if we start using Lambda or keep waiting for further development of the iotcore rule. Thanks!
We are also interested in this!
+1 for this. Any updates on a timeline? 08/2024
Come on it's been 3 years already. Routing through lambda isn't going to work if you have high volume of data ingestion because the costs of lambda are going to be more than having single values stored in timestream.
This issue needs to be a prioritized by the team.