Assign in bulk
The fastest way to get to zero-unowned is to bulk-assign:- By label match:
system=payments→ assign to the payments-team owner. - By naming pattern:
arn:aws:iam::*:role/lambda-*→ assign to the platform team. - By source account: everything in AWS account
123456789012→ assign to the account owner.
Delegation
Owners can nominate a delegate for a bounded window (vacation, incident response) from NHIG → Settings → Delegations → New. Provide the delegate’s email and an end date. During the window, review campaigns route to the delegate. The audit row still records the original owner-of-record.Attestation
An owner attests an identity by acknowledging in the UI that it’s legitimate and its permissions are appropriate. Open the identity row and click Attest — enter an optional reason (e.g. “reviewed for Q3 2026”). Attestations are timestamped and signed by the reviewer’s session token. The next review campaign’s SLA runs from the attestation date.Ownership graph
NHIG → Graph renders the identity → owner relationships as a searchable graph — useful for spotting single points of failure (one engineer owning 400 identities) or org-chart drift (identities owned by ex-employees still active in HR).Related
Access reviews
Campaigns force periodic re-attestation.
Findings
Unowned identities are always flagged.