Overview
Connect AWS IoT Core to automatically forward device telemetry data to Telemetron using IoT Rules. Telemetron provides a downloadable Terraform package that provisions all required AWS resources, including the IoT Rule, IAM roles, and HTTPS destination.Prerequisites
- An active AWS account with permissions to create IoT Rules, IAM roles, and rule destinations
- Terraform v1.0+ installed locally
- AWS CLI configured with appropriate credentials
- Devices publishing telemetry to MQTT topics in AWS IoT Core
Setup
Generate Configuration
Go to Settings > Integrations > AWS IoT Core and configure the following:
-
AWS Region — Select your target region:
Region Code Region Name us-east-1 US East (N. Virginia) us-east-2 US East (Ohio) us-west-1 US West (N. California) us-west-2 US West (Oregon) af-south-1 Africa (Cape Town) ap-east-1 Asia Pacific (Hong Kong) ap-south-1 Asia Pacific (Mumbai) ap-south-2 Asia Pacific (Hyderabad) ap-southeast-1 Asia Pacific (Singapore) ap-southeast-2 Asia Pacific (Sydney) ap-southeast-3 Asia Pacific (Jakarta) ap-southeast-4 Asia Pacific (Melbourne) ap-northeast-1 Asia Pacific (Tokyo) ap-northeast-2 Asia Pacific (Seoul) ap-northeast-3 Asia Pacific (Osaka) ca-central-1 Canada (Central) eu-central-1 Europe (Frankfurt) eu-central-2 Europe (Zurich) eu-west-1 Europe (Ireland) eu-west-2 Europe (London) eu-west-3 Europe (Paris) eu-south-1 Europe (Milan) eu-south-2 Europe (Spain) eu-north-1 Europe (Stockholm) me-south-1 Middle East (Bahrain) me-central-1 Middle East (UAE) sa-east-1 South America (São Paulo) -
IoT Rule Name — Enter a name using only letters, numbers, and underscores (e.g.,
telemetron_forward_rule) -
MQTT Topic Filters — Add one or more topic filters that match your device telemetry topics (e.g.,
device/+/telemetry). Click Add Filter to include additional patterns. - Enable CloudWatch Error Logging — Optionally toggle this on to log rule execution errors to CloudWatch for debugging.
Deploy with Terraform
Extract the downloaded ZIP file and deploy from your terminal:Review the plan output and type
yes to confirm the deployment. Terraform will create the IoT Rule, IAM role, and HTTPS rule destination in your AWS account.Confirm Destination
After Terraform completes, you must manually confirm the HTTPS rule destination:
- Open the AWS IoT Rule Destinations console in your selected region
- Find the destination created by Terraform and click on it
- Click Confirm and activate
- AWS sends a confirmation request to the Telemetron endpoint — a confirmation token will appear in the Telemetron integration page
- Copy the confirmation token from Telemetron
- Paste the token back into the AWS console confirmation dialog and submit
Configuration
Once connected, the integration page displays your organization’s configuration:| Field | Description |
|---|---|
| Webhook URL | https://admin.telemetron.ai/api/telemetry — the endpoint receiving forwarded telemetry |
| API Key | Your organization’s API key used to authenticate incoming telemetry data |
How It Works
When a device publishes a message to an MQTT topic that matches one of your configured filters, the AWS IoT Rule forwards the payload to Telemetron’s webhook endpoint over HTTPS. Telemetron ingests the telemetry data, associates it with the correct device, and makes it available to the AI support agent for diagnostics and troubleshooting.Troubleshooting
| Issue | Resolution |
|---|---|
| Rule name validation error | IoT Rule names can only contain letters, numbers, and underscores. Remove any hyphens, spaces, or special characters. |
| Destination not confirming | Ensure you complete the confirmation step manually in the AWS console. The destination will remain in a “Pending confirmation” state until the token exchange is completed. |
| Confirmation token not appearing | Check that the Terraform deployment completed successfully and that the destination URL points to https://admin.telemetron.ai/api/telemetry. |
| Token validation failed | Copy the token exactly as displayed in Telemetron — do not include any leading or trailing whitespace. |
| No telemetry data arriving | Verify your MQTT topic filters match the topics your devices publish to. Use the AWS IoT MQTT test client to confirm devices are publishing. |
| SSL/TLS errors | Ensure your AWS region supports TLS 1.2+. Check that no corporate proxy or firewall is blocking outbound HTTPS traffic from AWS IoT. |
| Authentication failures | Verify the API key in the Terraform configuration matches the key shown on the Telemetron integration page. Regenerate the key if needed. |