AWS iot-twinmaker documentation change
Summary
Updated documentation URLs to fix formatting (added double slashes after domain)
Security assessment
The changes only correct URL formatting by adding double slashes after the domain in documentation links. No security-related content was added or modified beyond existing references to security documentation for Timestream (which was already present before the URL formatting change).
Diff
diff --git a/iot-twinmaker/latest/guide/time-series-data-connectors.md b/iot-twinmaker/latest/guide/time-series-data-connectors.md index 1ff3c4617..792dec0f3 100644 --- a//iot-twinmaker/latest/guide/time-series-data-connectors.md +++ b//iot-twinmaker/latest/guide/time-series-data-connectors.md @@ -40 +40 @@ Before developing your time-series data connector, we recommend that you complet - * Create [AWS IoT TwinMaker component types](https://docs.aws.amazon.com/iot-twinmaker/latest/guide/twinmaker-component-types.html). + * Create [AWS IoT TwinMaker component types](https://docs.aws.amazon.com//iot-twinmaker/latest/guide/twinmaker-component-types.html). @@ -42 +42 @@ Before developing your time-series data connector, we recommend that you complet - * Create [AWS IoT TwinMaker entities](https://docs.aws.amazon.com/iot-twinmaker/latest/guide/twinmaker-gs-entity.html). + * Create [AWS IoT TwinMaker entities](https://docs.aws.amazon.com//iot-twinmaker/latest/guide/twinmaker-gs-entity.html). @@ -44 +44 @@ Before developing your time-series data connector, we recommend that you complet - * (Optional) Read [ Using and creating component types](https://docs.aws.amazon.com/iot-twinmaker/latest/guide/twinmaker-component-types.htm). + * (Optional) Read [ Using and creating component types](https://docs.aws.amazon.com//iot-twinmaker/latest/guide/twinmaker-component-types.htm). @@ -46 +46 @@ Before developing your time-series data connector, we recommend that you complet - * (Optional) Read [AWS IoT TwinMaker data connector interface](https://docs.aws.amazon.com/iot-twinmaker/latest/guide/data-connector-interface.html) to get a general understanding of AWS IoT TwinMaker data connectors. + * (Optional) Read [AWS IoT TwinMaker data connector interface](https://docs.aws.amazon.com//iot-twinmaker/latest/guide/data-connector-interface.html) to get a general understanding of AWS IoT TwinMaker data connectors. @@ -83 +83 @@ The following procedure outlines a development model that incrementally builds u -In a component type, you define common properties that are shared across your components. To learn more about defining component types, see [Using and creating component types](https://docs.aws.amazon.com/iot-twinmaker/latest/guide/twinmaker-component-types.html). +In a component type, you define common properties that are shared across your components. To learn more about defining component types, see [Using and creating component types](https://docs.aws.amazon.com//iot-twinmaker/latest/guide/twinmaker-component-types.html). @@ -467 +467 @@ There are multiple ways to test your Lambda connector: you can test the Lambda c -For more information on testing your Lambda functions, see [Testing Lambda functions](https://docs.aws.amazon.com/lambda/latest/dg/testing-functions.html) and [Locally testing AWS CDK applications](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-cdk-testing.html). +For more information on testing your Lambda functions, see [Testing Lambda functions](https://docs.aws.amazon.com//lambda/latest/dg/testing-functions.html) and [Locally testing AWS CDK applications](https://docs.aws.amazon.com//serverless-application-model/latest/developerguide/serverless-cdk-testing.html). @@ -471 +471 @@ For more information on testing your Lambda functions, see [Testing Lambda funct -For documentation on security best practices with Timestream, see [Security in Timestream](https://docs.aws.amazon.com/timestream/latest/developerguide/security.html). +For documentation on security best practices with Timestream, see [Security in Timestream](https://docs.aws.amazon.com//timestream/latest/developerguide/security.html). @@ -485 +485 @@ If you follow the setup instructions in the GitHub sample, all AWS IoT TwinMaker -We recommend having an integrated test with AWS IoT TwinMaker to verify the data plane query works end-to-end. You can perform that through [GetPropertyValueHistory](https://docs.aws.amazon.com/iot-twinmaker/latest/apireference/API_GetPropertyValueHistory.html) API or easily in [AWS IoT TwinMaker console](https://console.aws.amazon.com/iottwinmaker/). +We recommend having an integrated test with AWS IoT TwinMaker to verify the data plane query works end-to-end. You can perform that through [GetPropertyValueHistory](https://docs.aws.amazon.com//iot-twinmaker/latest/apireference/API_GetPropertyValueHistory.html) API or easily in [AWS IoT TwinMaker console](https://console.aws.amazon.com/iottwinmaker/). @@ -489 +489 @@ We recommend having an integrated test with AWS IoT TwinMaker to verify the data -In the AWS IoT TwinMaker console, go to **component details** and then under the **Test** , you’ll see all the properties in the component are listed there. The **Test** area of the console allows you to test time-series properties as well as non-time-series properties. For time-series properties you can also use the [ GetPropertyValueHistory](https://docs.aws.amazon.com/iot-twinmaker/latest/apireference/API_GetPropertyValueHistory.html) API and for non-time-series properties use [ GetPropertyValue](https://docs.aws.amazon.com/iot-twinmaker/latest/apireference/API_GetPropertyValue.html) API. If your Lambda connector supports multiple property query, you can choose more than one property. +In the AWS IoT TwinMaker console, go to **component details** and then under the **Test** , you’ll see all the properties in the component are listed there. The **Test** area of the console allows you to test time-series properties as well as non-time-series properties. For time-series properties you can also use the [ GetPropertyValueHistory](https://docs.aws.amazon.com//iot-twinmaker/latest/apireference/API_GetPropertyValueHistory.html) API and for non-time-series properties use [ GetPropertyValue](https://docs.aws.amazon.com//iot-twinmaker/latest/apireference/API_GetPropertyValue.html) API. If your Lambda connector supports multiple property query, you can choose more than one property. @@ -495 +495 @@ In the AWS IoT TwinMaker console, go to **component details** and then under the -You can now set up an [AWS IoT TwinMaker Grafana dashboard](https://docs.aws.amazon.com/iot-twinmaker/latest/guide/grafana-integration.html) to visualize metrics. You can also explore other data connector samples in the [AWS IoT TwinMaker samples GitHub repository ](https://github.com/aws-samples/aws-iot-twinmaker-samples/tree/main/src/modules/s3) to see if they fit your use case. +You can now set up an [AWS IoT TwinMaker Grafana dashboard](https://docs.aws.amazon.com//iot-twinmaker/latest/guide/grafana-integration.html) to visualize metrics. You can also explore other data connector samples in the [AWS IoT TwinMaker samples GitHub repository ](https://github.com/aws-samples/aws-iot-twinmaker-samples/tree/main/src/modules/s3) to see if they fit your use case.