Enable AWS IoT fleet indexing and query connected devices matching a shadow attribute using SearchIndex
domain: docs.aws.amazon.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call UpdateIndexingConfiguration (or aws iot update-indexing-configuration) to set thingIndexingConfiguration.thingIndexingMode to REGISTRY_AND_SHADOW
Separately set thingConnectivityIndexingMode to STATUS to index live connectivity state, since this is a distinct field from thingIndexingMode
Wait for indexing to catch up, then confirm via DescribeIndex/aws iot get-indexing-configuration
Run aws iot search-index with a query-string combining registry and shadow fields, e.g. connectivity.connected:true AND shadow.reported.attr:value
Paginate through results using max-results (up to 100 per page) and the returned nextToken
Known gotchas
there is no thingIndexingMode value called REGISTRY_AND_CONNECTIVITY_STATUS -- connectivity indexing is controlled by the separate thingConnectivityIndexingMode field
shadow queries only work for shadows covered by the current indexing mode; new shadow updates take a short propagation delay before appearing in the index
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?