AWS iot: Update IAM role and substitution template links for InfluxDB action
Summary
Updated cross-reference links: the IAM role prerequisite now points to the iot-create-role-iam anchor, and per-element substitution template references now point to the iot-substitution-templates array payload shorthand section.
Security assessment
The diff only changes hyperlink targets/anchors for IAM role and substitution template documentation. No new security guidance or vulnerability fix is introduced; the IAM mention is pre-existing text with only the link anchor changed.
Evidence
* **An IAM role** that AWS IoT can assume to write to your InfluxDB databases and perform the `GetSecretValue` operation on the secret that stores your InfluxDB credentials. For more information, see [Granting an AWS IoT rule the access it requires](./iot-create-role.html#iot-create-role-iam).
Diff
diff --git a/iot/latest/developerguide/influxdb-rule-action.md b/iot/latest/developerguide/influxdb-rule-action.md index 0471d5f99..21d4f05cd 100644 --- a//iot/latest/developerguide/influxdb-rule-action.md +++ b//iot/latest/developerguide/influxdb-rule-action.md @@ -42 +42 @@ This rule action has the following prerequisites: - * **An IAM role** that AWS IoT can assume to write to your InfluxDB databases and perform the `GetSecretValue` operation on the secret that stores your InfluxDB credentials. For more information, see [Granting an AWS IoT rule the access it requires](./iot-create-role.html). + * **An IAM role** that AWS IoT can assume to write to your InfluxDB databases and perform the `GetSecretValue` operation on the secret that stores your InfluxDB credentials. For more information, see [Granting an AWS IoT rule the access it requires](./iot-create-role.html#iot-create-role-iam). @@ -196 +196 @@ The InfluxDB action is metered based on the outbound payload size in 5 KiB incre -When your IoT devices send batched time-series data as a JSON array, you can use the **“per-element substitution templates”** to resolve values from each individual array element. This routes each data point to a different table or applies element-specific tags. For more information, see [Per-element templates](https://docs.aws.amazon.com/iot/latest/developerguide/per-element-templates.html). +When your IoT devices send batched time-series data as a JSON array, you can use the **“per-element substitution templates”** to resolve values from each individual array element. This routes each data point to a different table or applies element-specific tags. For more information, see [Per-element substitution for array payloads in AWS IoT rules](./iot-substitution-templates.html#iot-array-payload-shorthand). @@ -202 +202 @@ When your IoT devices send batched time-series data as a JSON array, you can use - * `@{expression}` – Resolves at element scope, against an individual element of the payload produced by the rule's SQL SELECT statement. Re-evaluated for each array element, so each point can get a different value. For more information, see [`@{expression}` reference](https://docs.aws.amazon.com/iot/latest/developerguide/per-element-expression.html). + * `@{expression}` – Resolves at element scope, against an individual element of the payload produced by the rule's SQL SELECT statement. Re-evaluated for each array element, so each point can get a different value. For more information, see [@{expression} reference](./iot-substitution-templates.html#iot-array-payload-shorthand).