9,634
edits
Changes
Template:Networking rutos manual cloud solutions (view source)
Revision as of 14:38, 8 October 2024
, 8 Octoberno edit summary
<td>.tar.gz file; default: <b>none</b></td>
<td>.tar.gz file; default: <b>none</b></td>
<td>Core-specific config file.</td>
<td>Core-specific config file.</td>
</tr>
</table>|#default=}}
==AWS IoT Core==
AWS IoT Core is a utility meant to interact with Amazon Web Services cloud platform. It provides AWS IoT Core Jobs support that lets the device be controlled from AWS IoT Core platform by using device's API.
To add new 'AWS job', press <b>Add</b> button:
[[File:Networking_rutos_manual_cloud_solutions_aws_iot_core_add.png|border|class=tlt-border]]
After that you will be redirected to AWS jobs thing configuration:
[[File:Networking_rutos_manual_cloud_solutions_aws_jobs_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td></td>
</tr>
<tr>
<td>Thing's name</td>
<td>string; default: <b>none</b></td>
<td>Thing's name on AWS IoT Core platform.</td>
</tr>
<tr>
<td>Endpoint</td>
<td>domain; default: <b>none</b></td>
<td>AWS IoT Core platform endpoint used to determine AWS account to connect to.</td>
</tr>
<tr>
<td>CA file</td>
<td>.ca file; default: <b>none</b></td>
<td>AWS CA certificate obtained from AWS IoT Core platform.</td>
</tr>
<tr>
<td>Thing's certificate</td>
<td>.crt file; default: <b>none</b></td>
<td>Thing's certificate obtained from AWS IoT Core platform.</td>
</tr>
<tr>
<td>Thing's private key</td>
<td>.key file; default: <b>none</b></td>
<td>Thing's private key obtained from AWS IoT Core platform.</td>
</tr>
<tr>
<td>Port</td>
<td>integer [1..65535]; default: <b>8883</b></td>
<td>MQTT port number.</td>
</tr>
<tr>
<td>QoS</td>
<td>At most once (0) {{!}} At least once (1); default: <b>At least once (1)</b></td>
<td>MQTT Quality of Service. Allowed values:
<ul>
<li><b>0</b> - when we prefer that the message will not arrive at all rather than arrive twice</li>
<li><b>1</b> - when we want the message to arrive at least once but don't care if it arrives twice (or more).</li>
</ul>
</td>
</tr>
<tr>
<td>Keepalive</td>
<td>integer [30..65535]; default: <b>120</b></td>
<td>MQTT keepalive time in seconds.</td>
</tr>
<tr>
<td>Max loops</td>
<td>integer [10..200]; default: <b>50</b></td>
<td>MQTT max loops - during initial subscription to topics the service has to wait for a successful subscription acknowledgement. The service performs mosquitto loops to wait for the answer. This option determines how many loops can be performed while waiting for subscription acknowledgement.</td>
</tr>
</tr>
</table>
</table>
[[Category:{{{name}}} Services section]]
[[Category:{{{name}}} Services section]]