- Newest
- Most votes
- Most comments
Thanks for the details regarding the question on the Rules Engine HTTP action. The confirmation process is required to ensure that unauthorized endpoints are not sent traffic from AWS IoT Core., hence the control plane method for sending the confirmation token as a specific query string (and body) key and value. The service logs in question would be with the endpoint, which in this case would be Telegram.
I haven't tested with Telegram but in looking at the API, my guess that since the API URI is https://{confirmation url}/?confirmationToken={confirmation token}
(where the URL could include the bot token id), it would still fail on only seeing the ?confirmationToken={confirmation token}
param/value without matching the API parameters.
One alternative is you could move the logic of sending messages to another rules action such as AWS Lambda (lambda action) or AWS Fargate (HTTP listener that then reformats the message and sends to Telegram via the HTTPS action and validation process above). So, store the credentials and logic to read the message from AWS IoT Core and transform to an HTTP POST that is valid for Telegram.
Interested in what you come up, please let me know how it works out.
Hi,
I've checked with Telegram Bot API and accessing the service logs isn't possible.
I've switch to AWS Lambda and it works!
Relevant content
- asked a year ago
- asked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago