Connect your Proxus devices to AWS IoT Core for secure data ingestion, device management, and leveraging AWS cloud services.
This document provides a step-by-step guide for integrating Proxus with AWS IoT Core. This integration allows you to connect your Proxus-managed devices to the AWS cloud, enabling secure data transfer, device management, and access to various AWS services.
A “Thing” in AWS IoT Core represents a physical or logical device.
Navigate to Manage > Things and click Create things.
Choose Create a single thing and click Next.
Provide a Thing name (e.g., proxus_demo
). Click Next.
Configure device certificate: Select Auto-generate a new certificate (recommended). Click Next.
Attach policies to certificate: Click Create thing without attaching any policies for now.
Download certificates and keys: Download the following files:
Important: Store the private key securely, as it cannot be downloaded again.
An IoT policy defines the permissions for your “Thing.”
Navigate to Security > Policies and click Create policy.
Provide a Policy name (e.g., proxus_policy
).
Policy document: Use the builder to add the following policy statements (replace resources with your account details):
Policy Effect | Policy Action | Policy Resource |
---|---|---|
Allow | iot:Connect | arn:aws:iot:${region}:${account}:client/${thingName} |
Allow | iot:Publish | arn:aws:iot:${region}:${account}:topic/enterprise/bits/data/process_cell/equipment/module/test |
Allow | iot:Subscribe | arn:aws:iot:${region}:${account}:topicfilter/enterprise/bits/data/process_cell/equipment/module/test |
Allow | iot:Receive | arn:aws:iot:${region}:${account}:topic/enterprise/bits/data/process_cell/equipment/module/test |
Click Create.
proxus_policy
). Click Attach policies.In Proxus, navigate to Integrations > Outbound Channels.
Click + New.
Select AWS IoT Core as the Target Type. Provide a Profile Name (e.g., AWS IoT Core
).
Parameters: Add the following parameters:
Key | Value | |
---|---|---|
EndPoint | Your AWS IoT Core domain name (e.g., xxxxxxxxxxxx-ats.iot.us-east-1.amazonaws.com) | |
Port | 8883 | |
ClientId | Your “Thing” name (e.g., proxus ) | |
UseTls | True | |
PfxCertificate | Upload the device certificates (xxx.certificate.pem.crt and xxx.private.pem.key file) you downloaded earlier. | |
QualityOfServiceLevel | AtLeastOnce | Ensures message delivery with confirmation (QoS 1) |
MaxReconnectAttempts | 10 | Number of reconnection attempts on failure |
HealthCheckIntervalSec | 10 | Interval for connection health checks |
KeepAliveSeconds | 30 | Keep-alive interval for MQTT connection |
Click Save.
enterprise/bits/data/process_cell/equipment/module/test
).Proxus automatically creates AWS IoT Core topics. It constructs these topics using the fields from the Hierarchy tab (except for Group) and appends the device name to the end. If these fields are left blank, the resulting topic will resemble: unknown/unknown/unknown/unknown/unknown/test
.
The following additional parameters can be configured for enhanced reliability:
Parameter | Description | Default Value |
---|---|---|
InitialReconnectDelayMs | Initial delay before first reconnection attempt (ms) | 1000 |
MaxReconnectDelayMs | Maximum delay between reconnection attempts (ms) | 30000 |
MessageBatchTimeoutMs | Time window for collecting messages into batches (ms) | 500 |
MaxBatchSize | Maximum number of messages to batch together | 50 |
ConnectionTimeoutSec | Timeout for connection attempts (seconds) | 5 |
The Proxus-AWS IoT integration includes these reliability features:
If you encounter issues with the integration:
You have successfully integrated Proxus with AWS IoT Core. Your Proxus devices can now securely communicate with AWS, enabling you to collect data, manage devices, and leverage the power of the AWS cloud.
Connect your Proxus devices to AWS IoT Core for secure data ingestion, device management, and leveraging AWS cloud services.
This document provides a step-by-step guide for integrating Proxus with AWS IoT Core. This integration allows you to connect your Proxus-managed devices to the AWS cloud, enabling secure data transfer, device management, and access to various AWS services.
A “Thing” in AWS IoT Core represents a physical or logical device.
Navigate to Manage > Things and click Create things.
Choose Create a single thing and click Next.
Provide a Thing name (e.g., proxus_demo
). Click Next.
Configure device certificate: Select Auto-generate a new certificate (recommended). Click Next.
Attach policies to certificate: Click Create thing without attaching any policies for now.
Download certificates and keys: Download the following files:
Important: Store the private key securely, as it cannot be downloaded again.
An IoT policy defines the permissions for your “Thing.”
Navigate to Security > Policies and click Create policy.
Provide a Policy name (e.g., proxus_policy
).
Policy document: Use the builder to add the following policy statements (replace resources with your account details):
Policy Effect | Policy Action | Policy Resource |
---|---|---|
Allow | iot:Connect | arn:aws:iot:${region}:${account}:client/${thingName} |
Allow | iot:Publish | arn:aws:iot:${region}:${account}:topic/enterprise/bits/data/process_cell/equipment/module/test |
Allow | iot:Subscribe | arn:aws:iot:${region}:${account}:topicfilter/enterprise/bits/data/process_cell/equipment/module/test |
Allow | iot:Receive | arn:aws:iot:${region}:${account}:topic/enterprise/bits/data/process_cell/equipment/module/test |
Click Create.
proxus_policy
). Click Attach policies.In Proxus, navigate to Integrations > Outbound Channels.
Click + New.
Select AWS IoT Core as the Target Type. Provide a Profile Name (e.g., AWS IoT Core
).
Parameters: Add the following parameters:
Key | Value | |
---|---|---|
EndPoint | Your AWS IoT Core domain name (e.g., xxxxxxxxxxxx-ats.iot.us-east-1.amazonaws.com) | |
Port | 8883 | |
ClientId | Your “Thing” name (e.g., proxus ) | |
UseTls | True | |
PfxCertificate | Upload the device certificates (xxx.certificate.pem.crt and xxx.private.pem.key file) you downloaded earlier. | |
QualityOfServiceLevel | AtLeastOnce | Ensures message delivery with confirmation (QoS 1) |
MaxReconnectAttempts | 10 | Number of reconnection attempts on failure |
HealthCheckIntervalSec | 10 | Interval for connection health checks |
KeepAliveSeconds | 30 | Keep-alive interval for MQTT connection |
Click Save.
enterprise/bits/data/process_cell/equipment/module/test
).Proxus automatically creates AWS IoT Core topics. It constructs these topics using the fields from the Hierarchy tab (except for Group) and appends the device name to the end. If these fields are left blank, the resulting topic will resemble: unknown/unknown/unknown/unknown/unknown/test
.
The following additional parameters can be configured for enhanced reliability:
Parameter | Description | Default Value |
---|---|---|
InitialReconnectDelayMs | Initial delay before first reconnection attempt (ms) | 1000 |
MaxReconnectDelayMs | Maximum delay between reconnection attempts (ms) | 30000 |
MessageBatchTimeoutMs | Time window for collecting messages into batches (ms) | 500 |
MaxBatchSize | Maximum number of messages to batch together | 50 |
ConnectionTimeoutSec | Timeout for connection attempts (seconds) | 5 |
The Proxus-AWS IoT integration includes these reliability features:
If you encounter issues with the integration:
You have successfully integrated Proxus with AWS IoT Core. Your Proxus devices can now securely communicate with AWS, enabling you to collect data, manage devices, and leverage the power of the AWS cloud.