You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 15, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: developerguide/create-manage-jobs.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Managing jobs<aname="create-manage-jobs"></a>
2
2
3
-
You can use the [AWS IoT console](https://console.aws.amazon.com/iot/), the Jobs HTTPS API, the AWS Command Line Interface, or the AWS SDKs to create and manage jobs\. For more information, see [Job management and control API](jobs-api.md#jobs-http-api), [AWS CLI Command Reference: iot](https://docs.aws.amazon.com/cli/latest/reference/iot/index.html) or [AWS SDKs and Tools](http://aws.amazon.com/tools/#sdk)\.
3
+
You can use the [AWS IoT console](https://console.aws.amazon.com/iot/), the Jobs HTTPS API, the AWS Command Line Interface, or the AWS SDKs to create and manage jobs\. For more information, see [Job management and control API](jobs-http-api.md), [AWS CLI Command Reference: iot](https://docs.aws.amazon.com/cli/latest/reference/iot/index.html) or [AWS SDKs and Tools](http://aws.amazon.com/tools/#sdk)\.
4
4
5
5
The primary purpose of jobs is to notify devices of a software or firmware update\. When sending code to devices, the best practice is to sign the code file\. This allows devices to detect if the code has been modified in transit\. The instructions in the following section are written with the assumption that you want to code\-sign the software update you are sending to your devices\.
6
6
@@ -14,7 +14,7 @@ When a device requests the job document, AWS IoT generates the presigned URL and
14
14
15
15
When you create a job that uses presigned Amazon S3 URLs, you must provide an IAM role that grants permission to download files from the Amazon S3 bucket where the data or updates are stored\. The role must also grant permission for AWS IoT to assume the role\.
16
16
17
-
You can specify an optional timeout for the presigned URL\. For more information, see [CreateJob](jobs-api.md#jobs-CreateJob)\.
17
+
You can specify an optional timeout for the presigned URL\. For more information, see [CreateJob](jobs-http-api.md#jobs-CreateJob)\.
18
18
19
19
**To grant the jobs service permission to assume your role**
Copy file name to clipboardExpand all lines: developerguide/dynamic-thing-groups.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ You can specify a dynamic thing group as a target for a job\. Only things that m
8
8
9
9
For example, suppose that you want to update the firmware on your devices, but, to minimize the chance that the update is interrupted, you only want to update firmware on devices with battery life greater than 80%\. You can create a dynamic thing group that only includes devices with a reported battery life above 80%, and you can use that dynamic thing group as the target for your firmware update job\. Only devices that meet your battery life criteria receive the firmware update\. As devices reach the 80% battery life criteria, they are added to the dynamic thing group and receive the firmware update\.
10
10
11
-
For more information about specifying thing groups as job targets, see [CreateJob](jobs-api.md#jobs-CreateJob)\.
11
+
For more information about specifying thing groups as job targets, see [CreateJob](jobs-http-api.md#jobs-CreateJob)\.
12
12
13
13
Dynamic thing groups differ from static thing groups in the following ways:
14
14
+ Thing membership is not explicitly defined\. To create a dynamic thing group, you must define a query string that defines group membership\.
Copy file name to clipboardExpand all lines: developerguide/iot-connect-devices.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Every customer has an `iot:Data-ATS` and an `iot:Data` endpoint\. Each endpoint
30
30
| IoT data |`iot:Data-ATS`| Used to send and receive data to and from the message broker, [Device Shadow](iot-device-shadows.md), and [Rules Engine](iot-rules.md) components of AWS IoT\.`iot:Data-ATS` returns an ATS signed data endpoint\.|
31
31
| IoT data \(legacy\)|`iot:Data`| iot:Data returns a VeriSign signed data endpoint provided for backward compatibility\.|
32
32
| IoT credential access |`iot:CredentialProvider`| Used to exchange a device's built\-in X\.509 certificate for temporary credentials to connect directly with other AWS services\. For more information about connecting to other AWS services, see [Authorizing Direct Calls to AWS Services](authorizing-direct-aws.md)\.|
33
-
| IoT job management |`iot:Jobs`| Used to enable devices to interact with the AWS IoT Jobs service using the [Jobs Device HTTPS APIs](jobs-api.md#jobs-mqtt-api)\.|
33
+
| IoT job management |`iot:Jobs`| Used to enable devices to interact with the AWS IoT Jobs service using the [Jobs Device HTTPS APIs](jobs-mqtt-api.md)\.|
34
34
35
35
You can also use your own fully\-qualified domain name \(FQDN\), such as *example\.com*, and the associated server certificate to connect devices to AWS IoT by using [Configurable endpoints \(beta\)](iot-custom-endpoints-configurable.md), which is currently in public beta\.
Copy file name to clipboardExpand all lines: developerguide/iot-ddb-rule.md
+33-7
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,19 @@ The DynamoDB action allows you to take information from an incoming MQTT message
15
15
We do not recommend the use of personally identifiable information in rule names or descriptions\.
16
16
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/iot/latest/developerguide/images/create-a-ddb-rule.png)
17
17
18
-
1.Under **Rule query statement**, choose the latest version from the **Using SQL version** list\. For **Rule query statement**, enter:
18
+
1.
19
19
20
-
```
21
-
SELECT * FROM 'my/greenhouse'
22
-
```
20
+
1. Under **Rule query statement**, choose the latest version from the **Using SQL version** list\. For **Rule query statement**, enter:
21
+
22
+
```
23
+
SELECT * FROM 'my/greenhouse'
24
+
```
25
+
26
+
`"SELECT *"` specifies that you want to send the entire MQTT message that initiated the rule\.
23
27
24
-
\(`"SELECT *"` specifies that you want to send the entire MQTT message that initiated the rule\.`"FROM 'my/greenhouse'"` tells the rules engine to initiate this rule when an MQTT message whose topic matches this topic filter is received\. Choose **Add action\.**
28
+
`"FROM 'my/greenhouse'"` tells the rules engine to initiate this rule when an MQTT message whose topic matches this topic filter is received\.
29
+
30
+
1. Choose **Add action**\.
25
31
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/iot/latest/developerguide/images/rule-query-ddb.png)
26
32
27
33
1. On **Select an action**, choose **Insert a message into a DynamoDB table**, and then choose **Configure action**\.
@@ -33,10 +39,30 @@ We do not recommend the use of personally identifiable information in rule names
33
39
1. On the **Amazon DynamoDB** page, choose **Create table**\.
34
40
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/iot/latest/developerguide/images/dynamodb-welcome.png)
35
41
36
-
1. On **Create DynamoDB table**, enter a name\. In **Partition key**, enter **Row**\. Select **Add sort key**, and then enter **PositionInRow** in the **Sort key** field\.`Row` represents a row of plants in a greenhouse\.`PositionInRow` represents the position of a plant in the row\. Choose **String** for both the partition and sort keys, and then choose **Create**\. It takes a few seconds to create your DynamoDB table\. Close the browser tab where the Amazon DynamoDB console is open\. If you don't close the tab, your DynamoDB table is not displayed in the **Table name** list on the **Configure action** page of the AWS IoT console\.
42
+
1.
43
+
44
+
1. On **Create DynamoDB table**, enter a name\. In **Partition key**, enter **Row**\.
45
+
46
+
1. Select **Add sort key**, and then enter **PositionInRow** in the **Sort key** field\. `Row` represents a row of plants in a greenhouse\. `PositionInRow` represents the position of a plant in the row\.
47
+
48
+
1. Choose **String** for both the partition and sort keys, and then choose **Create**\. It takes a few seconds to create your DynamoDB table\.
49
+
50
+
1. Close the browser tab where the Amazon DynamoDB console is open\. If you don't close the tab, your DynamoDB table is not displayed in the **Table name** list on the **Configure action** page of the AWS IoT console\.
37
51
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/iot/latest/developerguide/images/create-ddb-table.png)
38
52
39
-
1. On **Configure action**, choose your new table from the **Table name** list\. In **Partition key value**, enter **$\{row\}**\. This instructs the rule to take the value of the `row` attribute from the MQTT message and write it into the **Row** column in the DynamoDB table\. In **Sort key value**, enter **$\{pos\}**\. This writes the value of the `pos` attribute into the **PositionInRow** column\. In **Write message data to this column**, enter **Payload**\. This inserts the message payload into the `Payload` column\. Leave **Operation** blank\. This field allows you to specify which operation \(INSERT, UPDATE, or DELETE\) you want to perform when the action is initiated\. Choose **Create a new role**\.
53
+
1.
54
+
55
+
1. On **Configure action**, choose your new table from the **Table name** list\.
56
+
57
+
1. In **Partition key value**, enter **$\{row\}**\. This instructs the rule to take the value of the `row` attribute from the MQTT message and write it into the **Row** column in the DynamoDB table\.
58
+
59
+
1. In **Sort key value**, enter **$\{pos\}**\. This writes the value of the `pos` attribute into the **PositionInRow** column\.
60
+
61
+
1. In **Write message data to this column**, enter **Payload**\. This inserts the message payload into the `Payload` column\.
62
+
63
+
1. Leave **Operation** blank\. Because you specified a value in the **Write message data to this column** field, the **Operation** must be blank\. This field allows you to specify which operation \(INSERT, UPDATE, or DELETE\) you want to perform when the action is initiated; however, entering **Payload** in **Write message data to this column** indicates that this rule action will perform an INSERT operation\.
64
+
65
+
1. Choose **Create a new role**\.
40
66
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/iot/latest/developerguide/images/configure-action-with-resource.png)
41
67
42
68
1. In **Create a new role**, enter a unique name, and then choose **Create role**\.
Copy file name to clipboardExpand all lines: developerguide/iot-embedded-c-sdk.md
+11-5
Original file line number
Diff line number
Diff line change
@@ -6,11 +6,11 @@ This section describes how to run the AWS IoT Device SDK for Embedded C\.
6
6
7
7
The AWS IoT Device SDK for Embedded C is generally targeted at resource constrained devices that require an optimized C language runtime\. You can use the SDK on any operating system and host it on any processor type \(for example, MCUs and MPUs\)\. If you have more memory and processing resources available, we recommend that you use one of the higher order AWS IoT Device and Mobile SDKs \(for example, C\+\+, Java, JavaScript, and Python\)\.
8
8
9
-
In general, the AWS IoT Device SDK for Embedded C is intended for systems that use MCUs or low\-end MPUs that run embedded operating systems\. For programming examples in the documentation, we use Raspberry Pi running embedded Linux\.
9
+
In general, the AWS IoT Device SDK for Embedded C is intended for systems that use MCUs or low\-end MPUs that run embedded operating systems\. For the programming example in this section, we assume your device uses Linux\.
10
10
11
11
**Example**
12
12
13
-
1. Download the AWS IoT Device SDK for Embedded C to your Raspberry Pi from [GitHub](https://github.com/aws/aws-iot-device-sdk-embedded-C)\.
13
+
1. Download the AWS IoT Device SDK for Embedded C to your device from [GitHub](https://github.com/aws/aws-iot-device-sdk-embedded-C)\.
@@ -41,7 +41,7 @@ Device and root CA certificates are subject to expiration or revocation\. If the
41
41
42
42
1. You must configure the sample with your personal AWS IoT Core endpoint, private key, certificate, and root CA certificate\. Navigate to the `aws-iot-device-sdk-embedded-c/demos/mqtt/mqtt_demo_mutual_auth` directory\.
43
43
44
-
If you have the AWS CLI installed, you can use the aws iot describe\-endpoint \-\-endpoint\-type iot:Data\-ATS command to find your personal endpoint URL\. If you don't have the AWS CLI installed, open your [AWS IoT console](https://console.aws.amazon.com/iot/home)\. From the navigation pane, choose **Manage**, and then choose **Things**\. Choose the IoT thing for your Raspberry Pi, and then choose **Interact**\. Your endpoint is displayed in the ** HTTPS** section of the thing details page\.
44
+
If you have the AWS CLI installed, you can use the aws iot describe\-endpoint \-\-endpoint\-type iot:Data\-ATS command to find your personal endpoint URL\. If you don't have the AWS CLI installed, open your [AWS IoT console](https://console.aws.amazon.com/iot/home)\. From the navigation pane, choose **Manage**, and then choose **Things**\. Choose the IoT thing for your device, and then choose **Interact**\. Your endpoint is displayed in the ** HTTPS** section of the thing details page\.
45
45
46
46
1. Open the `demo_config.h` file and update the values for the following:
47
47
AWS\_IOT\_ENDPOINT
@@ -101,7 +101,13 @@ Your private key file name, for example `certificates/private.pem.key`\.
101
101
102
102
**To run the AWS IoT Device SDK for Embedded C sample applications**
103
103
104
-
1. Navigate to `aws-iot-device-sdk-embedded-c/build`, then enter the following CMake command to generate the Makefiles needed to build\.
104
+
1. Navigate to `aws-iot-device-sdk-embedded-c` and create a build directory\.
105
+
106
+
```
107
+
mkdir build && cd build
108
+
```
109
+
110
+
1. Enter the following CMake command to generate the Makefiles needed to build\.
105
111
106
112
```
107
113
cmake ..
@@ -123,6 +129,6 @@ Your private key file name, for example `certificates/private.pem.key`\.
123
129
You should see output similar to the following:
124
130
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/iot/latest/developerguide/images/successful-run2.png)
125
131
126
-
Your Raspberry Pi is now connected to AWS IoT using the AWS IoT Device SDK for Embedded C\.
132
+
Your device is now connected to AWS IoT using the AWS IoT Device SDK for Embedded C\.
127
133
128
134
You can also use the AWS IoT console to view the MQTT messages that the sample app is publishing\. For information about how to use the MQTT client in the [AWS IoT console](https://console.aws.amazon.com/iot/home), see [View MQTT messages with the AWS IoT MQTT client](view-mqtt-messages.md)\.
Copy file name to clipboardExpand all lines: developerguide/iot-sdks.md
-3
Original file line number
Diff line number
Diff line change
@@ -66,10 +66,7 @@ The AWS IoT Device SDK for Embedded C is generally targeted at resource constrai
66
66
67
67
For more information, see the following:
68
68
+[AWS IoT Device SDK for Embedded C on GitHub](https://github.com/aws/aws-iot-device-sdk-embedded-C)
69
-
70
-
[AWS IoT Device SDK for Embedded C on GitHub](https://github.com/aws/aws-iot-device-sdk-embedded-C)
71
69
+[ AWS IoT Device SDK for Embedded C Readme](https://github.com/aws/aws-iot-device-sdk-embedded-C#aws-iot-device-sdk-for-embedded-c)
72
-
+[AWS IoT Device SDK for Embedded C Readme](https://github.com/aws/aws-iot-device-sdk-embedded-C#aws-iot-device-sdk-for-embedded-c)
73
70
+[AWS IoT Device SDK for Embedded C Samples](https://docs.aws.amazon.com/freertos/latest/lib-ref/embedded-csdk/202009.00/lib-ref/docs/doxygen/output/html/demos_main.html)
0 commit comments