Secure export to AWS IoT Core using MQTT with X.509 certificate authentication. Integrates seamlessly with AWS IoT services like Device Shadows, Thing Registry, and Rules Engine for cloud-based IoT solutions.
open_in_new
AWS IoT Core Documentation
amazon.com/iot-core
Configuration Parameters
| Parameter | Required | Type | Default | Description |
|---|---|---|---|---|
| EndPoint | Yes | string | - | AWS IoT Core endpoint (e.g., abcdef12345678-ats.iot.us-east-1.amazonaws.com). |
| ClientId | Yes | string | - | Unique client identifier for the connection. |
| CertificateThumbprint | Yes | string | - | Reference to the client certificate stored in the Certificate Store. |
| Port | No | int | 8883 | MQTT over TLS port (default is 8883). |
| UseTls | No | bool | true | Enable TLS encryption (should remain true for AWS IoT). |
| ValueMode | No | string | MeasureValueFields | Data serialization mode: MeasureValueFields or siemens. |
| QualityOfServiceLevel | No | int | 1 | MQTT QoS level (0, 1, 2). |
| MaxReconnectAttempts | No | int | 10 | Maximum reconnect attempts before backing off. |
| InitialReconnectDelayMs | No | int | 1000 | Initial reconnect delay in milliseconds. |
| MaxReconnectDelayMs | No | int | 30000 | Max reconnect delay in milliseconds. |
| MessageBatchTimeoutMs | No | int | 500 | Batch window for outbound publish. |
| MaxBatchSize | No | int | 50 | Max messages per batch. |
| HealthCheckIntervalSec | No | int | 5 | Connection health check interval. |
| ConnectionTimeoutSec | No | int | 5 | MQTT connection timeout. |
[!NOTE] AWS IoT Core requires a valid client certificate with its private key. Upload the certificate to the Certificate Store first, then assign it from the target parameter editor. Proxus generates the runtime payload automatically.
Certificate Assignment Flow
- Open Administration → Certificate Store
- Import the AWS client certificate as PFX or PEM + private key
- Open the AWS IoT Core outbound connector
- Use Edit Parameters and select the certificate from the certificate picker
- Save the connector
If the selected certificate does not include a private key, the connector cannot establish TLS authentication with AWS IoT Core.
Message Format
Each payload entry is sent as a flat JSON message. The format matches the Azure IoT connector for consistency.
Default Mode (MeasureValueFields)
{
"deviceId": "dev-1",
"deviceName": "sensor-1",
"measureName": "Temperature",
"timestamp": "2024-02-01T00:00:00.000Z",
"measureValueType": "DOUBLE",
"measureValueDouble": 25.5
}Siemens Mode (siemens)
{
"deviceId": "dev-22",
"deviceName": "line-2",
"measureName": "Status",
"timestamp": "2024-02-02T10:15:30.000Z",
"measureValueType": "BOOLEAN",
"value": "true"
}Internal Behavior
Authentication & Security
- X.509 Certificates: Uses AWS IoT Core's recommended X.509 certificate authentication
- TLS 1.2: Mandatory TLS encryption with certificate validation
- Device Identity: Each connection represents a unique IoT device in the registry
Performance Features
- MQTT Protocol: Uses standard MQTT for efficient IoT communication
- Message Serialization: Flexible data serialization supporting flat message structures
- Connection Management: Robust connection handling with automatic reconnection
- AWS Service Integration: Ready for integration with AWS IoT Rules, Lambda triggers, and DynamoDB