Jump to content
  • EN

Template:Networking rutos manual cloud solutions: Difference between revisions

← Older editNewer edit →
VisualWikitext
No edit summary
No edit summary
(3 intermediate revisions by the same user not shown)
Line 17: Line 17:


<u><b>Note:</b> Each Cloud Solutions service, except RMS, is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
<u><b>Note:</b> Each Cloud Solutions service, except RMS, is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
| series    = {{{series}}}
}}


==RMS==
==RMS==
Line 44: Line 40:
             <ul>
             <ul>
                 <li><b>Enabled</b> - RMS functionality is always on. When disconnected from RMS, the device will try connecting every 2-5 minutes (every 2 minutes the first hour; then every 5 minutes). If the device is disconnected from RMS for 14 days, it will go into Standby mode. When trying to connect to rms without internet connection, the router will try to reestablish connection every 10 seconds.</li>
                 <li><b>Enabled</b> - RMS functionality is always on. When disconnected from RMS, the device will try connecting every 2-5 minutes (every 2 minutes the first hour; then every 5 minutes). If the device is disconnected from RMS for 14 days, it will go into Standby mode. When trying to connect to rms without internet connection, the router will try to reestablish connection every 10 seconds.</li>
                 <li><b>Standby</b> - The device tries to establish a connection with the server infrequently (6 hours in-between attempts). This is done in order to reduce mobile traffic. In order to start using RMS, user intervention is not necessary from the device's side. Worst case scenario - RMS connection will be established 6 hours after the device was added to RMS.</li>
                 <li><b>Standby</b> - The device tries to establish a connection with the server infrequently (6 hours in-between attempts). This is done in order to reduce mobile traffic. In order to start using RMS, user intervention is not necessary from the device's side. Worst case scenario - RMS connection will be established 6 hours after the device was added to RMS. {{#ifeq: {{{name}}} | RUT241 | <b>Note:</b> RMS is automatically set to Standby mode if the eSIM Bootstrap profile is installed on the device.|}}</li>
                 <li><b>Disabled</b> - RMS functionality is completely disabled; therefore, no connection attempts are made. In order to start using RMS, the user must enable the service on the device's side.</li>
                 <li><b>Disabled</b> - RMS functionality is completely disabled; therefore, no connection attempts are made. In order to start using RMS, the user must enable the service on the device's side.</li>
             </ul>
             </ul>
Line 348: Line 344:
==AWS IoT Core==
==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.
AWS IoT Core is a utility meant to interact with Amazon Web Services cloud platform. It provides AWS IoT Core Jobs support and AWS Provisioning 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:
===AWS Job===


[[File:Networking_rutos_manual_cloud_solutions_aws_iot_core_add.png|border|class=tlt-border]]
To add new 'AWS job', press <b>Add</b> button and enter Thing's name:
 
[[File:Networking_rutos_manual_cloud_solutions_aws_iot_core_add_v1.png|border|class=tlt-border]]


After that you will be redirected to AWS jobs thing configuration:
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]]
[[File:Networking_rutos_manual_cloud_solutions_aws_jobs_configuration_v1.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 383: Line 381:
         <td>.ca file; default: <b>none</b></td>
         <td>.ca file; default: <b>none</b></td>
         <td>AWS CA certificate obtained from AWS IoT Core platform.</td>
         <td>AWS CA certificate obtained from AWS IoT Core platform.</td>
    </tr>
    <tr>
        <td>Provisioning</td>
        <td>provisioning configuration; default: <b>Basic provisioning</b></td>
        <td>AWS provisioning configuration to use. It can be configured in AWS provisiong page. If basic provisioning is used, Thing's certificate and private key must be uploaded.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 418: Line 421:
         <td>integer [10..200]; default: <b>50</b></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>
         <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>
</table>
===AWS Provisioning===
To add new 'AWS provisioning' template, press <b>Add</b> button and enter Template name:
[[File:Networking_rutos_manual_cloud_solutions_aws_iot_core_add_provisioning.png|border|class=tlt-border]]
After that you will be redirected to AWS provisioning configuration:
[[File:Networking_rutos_manual_cloud_solutions_aws_provisioning_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
        <td>Template</td>
        <td>string; default: <b></b></td>
        <td>Name of Fleet provisioning template in AWS service.</td>
    </tr>
    <tr>
        <td>Fleet provisioning type</td>
        <td><span style="color:blue">Provisioning by claim</span> {{!}} Provisioning by trusted user; default: <b>Provisioning by claim</b></td>
        <td></td>
    </tr>
    <tr>
        <td>Creation type</td>
        <td>CreateKeysAndCertificate {{!}} CreateCertificateFromCsr; default: <b>CreateKeysAndCertificate</b></td>
        <td>Specifies the AWS API to be used for certificate creation.</td>
    </tr>
    <tr>
        <td><span style="color:blue">Provisioning claim certificate</span></td>
        <td>.crt file; default: <b>none</b></td>
        <td>Provisioning claim certificate</td>
    </tr>
    <tr>
        <td><span style="color:blue">Provisioning claim private key</span></td>
        <td>.key file; default: <b>none</b></td>
        <td>Provisioning claim private key</td>
    </tr>
    <tr>
        <td><span style="color:red">Access key</span></td>
        <td>string (Values of 20 symbols are accepted. Following characters are accepted: A-Z0-9); default: <b>none</b></td>
        <td>Trusted user's access key.</td>
    </tr>
    <tr>
        <td><span style="color:red">Secret key</span></td>
        <td>string (Values of 40 symbols are accepted); default: <b>none</b></td>
        <td>Trusted user's secret key.</td>
    </tr>
    <tr>
        <td>Parameters</td>
        <td>string (Following characters are accepted: a-zA-Z0-9:%_-); default: <b>none</b></td>
        <td>Parameters which will be sent along with the certificate creation request. They will be formatted as JSON values ("Key": "Value").</td>
     </tr>
     </tr>
</table>
</table>


[[Category:{{{name}}} Services section]]
[[Category:{{{name}}} Services section]]
Retrieved from "https://wiki.teltonika-networks.com/view/Template:Networking_rutos_manual_cloud_solutions"