Hey, thanks for reaching out. Can you provide more details on the alarm model that you created? Did you define a "key" for that Alarm Model? If so, is that key path present in the payload of your input message?
I am no longer having this problem - I believe I may have had some mix up in permissions on my side, but this error is no longer arising (It seems I am getting past this error and then hitting the "key not found" error in my other posts. Closing this - tks!
Errors at dimensions (empty value) in Timestream from an IoT RuleAccepted Answerasked a year ago
Iot Core -> SiteWise ingestion questionAccepted Answerasked 9 months ago
Signature Does Not Match Error when sending to S3 from an AWS IoT client.asked 2 years ago
IoT Events - Calculating Moving Averages from InputsAccepted Answerasked 4 months ago
AWS IoT Rule to send MQTT message to DynamoDB not workingAccepted Answerasked 7 months ago
Add LoRaWAN gateway to AWS IoT Core - Permission/Role not acceptedAccepted Answerasked 7 months ago
Authoriztion failure when publishing to IoT Core MQTT topicAccepted Answerasked 2 months ago
Launch an instance with preconfigured alarmAccepted Answerasked 4 years ago
Potential Bug when attaching new alarm model to inputasked 2 years ago
When should I use IoT Core?asked 10 months ago