Unresolved references¶

Section 11 · From docs/INVENTORY_REFERENCE.md on GitHub

InventoryResult.unresolved_references and the unresolved_references arrays of inventory-map.json and inventory-dependencies.json. One entry per declared relation whose target matched no asset and no unmapped account. Capped at 2000 entries per run.

Key	Type	Meaning
`source`	`str`	`arn` of the declaring asset (its `id` when it has no `arn`).
`source_name`	`str`	`name` of the declaring asset.
`target`	`str`	The identifier that did not resolve.
`edge_type`	`str`	The edge type that would have been created.

[
  {
    "source": "arn:aws:lambda:us-east-1:123456789012:function:orders-worker",
    "source_name": "orders-worker",
    "target": "arn:aws:logs:us-east-1:123456789012:log-group:/aws/lambda/orders-worker",
    "edge_type": "LOGS_TO"
  }
]

Typical causes: a resource that was deleted but is still configured (a DLQ, a log group, a role), a service family excluded with --exclude-services, a region not collected, or a resource type no collector or sweep returns. Each one is worth a look: a deleted DLQ or a missing log group is often a real misconfiguration.