AWS iot: Fix broken documentation URLs for IoT location indexing
Summary
Corrected multiple broken hyperlinks by removing double slashes in AWS documentation URLs.
Security assessment
The change fixes broken URLs but doesn't address security vulnerabilities, modify security configurations, or reference CVEs.
Evidence
+You can use [AWS IoT fleet indexing](https://docs.aws.amazon.com/iot/latest/developerguide/iot-indexing.html) to index your devices' last sent location data and search for devices using geoqueries. This feature resolves device monitoring and management use cases such as location tracking and proximity search. Location indexing works similarly to other fleet indexing features, and with additional configurations to specify in your [thing indexing](./managing-fleet-index.html).
Diff
diff --git a/iot/latest/developerguide/location-indexing-geoquery.md b/iot/latest/developerguide/location-indexing-geoquery.md index 3fe5b0d68..392e2d847 100644 --- a//iot/latest/developerguide/location-indexing-geoquery.md +++ b//iot/latest/developerguide/location-indexing-geoquery.md @@ -11 +11 @@ Supported data formatsHow to index location dataUpdate thing indexing configurat -You can use [AWS IoT fleet indexing](https://docs.aws.amazon.com//iot/latest/developerguide/iot-indexing.html) to index your devices' last sent location data and search for devices using geoqueries. This feature resolves device monitoring and management use cases such as location tracking and proximity search. Location indexing works similarly to other fleet indexing features, and with additional configurations to specify in your [thing indexing](./managing-fleet-index.html). +You can use [AWS IoT fleet indexing](https://docs.aws.amazon.com/iot/latest/developerguide/iot-indexing.html) to index your devices' last sent location data and search for devices using geoqueries. This feature resolves device monitoring and management use cases such as location tracking and proximity search. Location indexing works similarly to other fleet indexing features, and with additional configurations to specify in your [thing indexing](./managing-fleet-index.html). @@ -77 +77 @@ At a minimum need, enable thing (registry) indexing configuration. You must also -Depending on your use cases, create geoqueries and run them to search for devices. The geoqeury you compose must follow the [Query syntax](https://docs.aws.amazon.com//iot/latest/developerguide/query-syntax.html). You can find some examples in Example geoqueries. +Depending on your use cases, create geoqueries and run them to search for devices. The geoqeury you compose must follow the [Query syntax](https://docs.aws.amazon.com/iot/latest/developerguide/query-syntax.html). You can find some examples in Example geoqueries. @@ -86 +86 @@ To index location data, you must update indexing configuration and include your -If your location data is stored in a classic shadow, you must set `thingIndexingMode` to be `REGISTRY_AND_SHADOW` and specify your location data in the `geoLocations` fields (`name` and `order`) in [`filter`](https://docs.aws.amazon.com//iot/latest/apireference/API_IndexingFilter.html). +If your location data is stored in a classic shadow, you must set `thingIndexingMode` to be `REGISTRY_AND_SHADOW` and specify your location data in the `geoLocations` fields (`name` and `order`) in [`filter`](https://docs.aws.amazon.com/iot/latest/apireference/API_IndexingFilter.html). @@ -115 +115 @@ Indexing filter provides additional selections for named shadows and geolocation -The list of geolocation targets that you select to index. The default maximum number of geolocation targets for indexing is `1`. To increase the limit, see [AWS IoT Device Management Quotas](https://docs.aws.amazon.com//general/latest/gr/iot_device_management.html#fleet-indexing-limits). +The list of geolocation targets that you select to index. The default maximum number of geolocation targets for indexing is `1`. To increase the limit, see [AWS IoT Device Management Quotas](https://docs.aws.amazon.com/general/latest/gr/iot_device_management.html#fleet-indexing-limits). @@ -128 +128 @@ The order of the geolocation target field. Valid values: `LatLon` and `LonLat`. -If your location data is stored in a named shadow, set `namedShadowIndexingMode` to be `ON`, add your named shadow name(s) to the `namedShadowNames` field in [`filter`](https://docs.aws.amazon.com//iot/latest/apireference/API_IndexingFilter.html), and specify your location data path in the `geoLocations` field in [`filter`](https://docs.aws.amazon.com//iot/latest/apireference/API_IndexingFilter.html). +If your location data is stored in a named shadow, set `namedShadowIndexingMode` to be `ON`, add your named shadow name(s) to the `namedShadowNames` field in [`filter`](https://docs.aws.amazon.com/iot/latest/apireference/API_IndexingFilter.html), and specify your location data path in the `geoLocations` field in [`filter`](https://docs.aws.amazon.com/iot/latest/apireference/API_IndexingFilter.html). @@ -161 +161 @@ Indexing filter provides additional selections for named shadows and geolocation -The list of geolocation targets that you select to index. The default maximum number of geolocation targets for indexing is `1`. To increase the limit, see [AWS IoT Device Management Quotas](https://docs.aws.amazon.com//general/latest/gr/iot_device_management.html#fleet-indexing-limits). +The list of geolocation targets that you select to index. The default maximum number of geolocation targets for indexing is `1`. To increase the limit, see [AWS IoT Device Management Quotas](https://docs.aws.amazon.com/general/latest/gr/iot_device_management.html#fleet-indexing-limits).