Aws/dns Observation
Observe Route53 hosted zones, record sets, and detect orphaned DNS records pointing at decommissioned infrastructure.
This model reads Route53 data for observation and cross-references record targets against inventory/adopt data to find orphaned entries. It does not manage zones or records — use @swamp/aws/route53 for infrastructure management.
Quick Start
swamp extension pull @webframp/aws/dns-observation
swamp model create @webframp/aws/dns-observation aws-dns-observation
swamp model method run aws-dns-observation list_zones
swamp model method run aws-dns-observation list_records
swamp model method run aws-dns-observation detect_orphansMethods
- list_zones — List all hosted zones with record counts and metadata
- list_records — List all record sets across zones (primary drift-state output)
- detect_orphans — Cross-reference records against inventory to find orphans
Prerequisites
Route53 read access. Required IAM permissions:
- route53:ListHostedZones
- route53:GetHostedZone
- route53:ListResourceRecordSets
- sts:GetCallerIdentity
For orphan detection, upstream models must have fresh data:
- @webframp/aws/inventory (scan spec) — EC2 IPs, ELBs, S3, CloudFront
- @webframp/aws/adopt (discovery spec) — Elastic IPs
2026.11.20.1
Changed: Bump @aws-sdk/* 3.1164.0 → 3.1173.0 (3 packages)
2026.11.10.1
Changed: Bump @aws-sdk/* 3.1139.0 → 3.1164.0 (3 packages)
2026.11.03.1
Changed: Bump zod 4.6.5 → 4.6.7
2026.10.28.1
Fixed: list_records reported status: succeeded with zonesScanned
counting a zone even when that zone's records could not be read. A zone passed
in zoneFilter whose ListResourceRecordSets call failed (for example, a zone
name supplied where a hosted zone ID is required) produced
totalRecords: 0, zonesScanned: 1 — indistinguishable from a successful scan
of a legitimately empty zone. zonesScanned now counts only zones whose
records were actually read.
Added: summary.zonesFailed: string[] lists the zone IDs whose
ListResourceRecordSets call failed, so callers can assert on read failures
instead of parsing log warnings.
Changed: When an explicit zoneFilter is given and none of its zones can
be read, list_records now throws instead of writing a zero-record success.
The error names the failed zones and reminds the caller that zoneFilter
expects hosted zone IDs, not names. A legitimately empty zone (read succeeds,
returns no records) is unaffected and still reports success. A partial failure
(some zones readable, some not) still succeeds, with the unreadable zones listed
in zonesFailed.
Upgrade note: Additive schema change. summary.zonesFailed defaults to
[], so resources stored by earlier versions still validate on read. Consumers
that computed success from zonesScanned alone should also check zonesFailed.
2026.10.14.1
Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.
Upgrade note: Metadata only. No code, schema, or behavioral changes.
2026.10.13.1
Fixed: list_zones and detect_orphans failed on current swamp with
Data name 'latest' is reserved for internal use. list_zones now writes its
zones resource as zone-scan and detect_orphans writes orphans as
orphan-scan, matching list_records' record-scan. list_records is
unchanged.
Changed: The stored data names changed. Anything that addressed the old
latest data name, for example data.latest("<model>", "latest") or
name == "latest", must use zone-scan / orphan-scan. The README query
examples named the spec (zones, orphans) rather than the data name, so they
never matched; they now use the real names. Resource specs and schemas are
unchanged, so consumers that select by spec are unaffected.
2026.09.24.1
Changed: Bump @aws-sdk/* 3.1133.0 → 3.1139.0 (3 packages)
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
Global Arguments
| Argument | Type | Description |
|---|---|---|
| region? | string | AWS region (Route53 is global but STS needs a region) |
| Argument | Type | Description |
|---|---|---|
| includePrivate? | boolean | Include private hosted zones in results |
| Argument | Type | Description |
|---|---|---|
| zoneFilter? | array | Limit to specific zone IDs. Omit for all zones. |
| typeFilter? | array | Limit to specific record types (A, AAAA, CNAME, etc.) |
| Argument | Type | Description |
|---|---|---|
| inventoryModelName? | string | Name of the @webframp/aws/inventory model instance |
| adoptModelName? | string | Name of the @webframp/aws/adopt model instance |
| skipTypes? | array | Record types to skip during orphan detection |
Resources
2026.11.10.1
Changed: Bump @aws-sdk/* 3.1139.0 → 3.1164.0 (3 packages)
2026.11.03.1
Changed: Bump zod 4.6.5 → 4.6.7
2026.10.28.1
Fixed: list_records reported status: succeeded with zonesScanned
counting a zone even when that zone's records could not be read. A zone passed
in zoneFilter whose ListResourceRecordSets call failed (for example, a zone
name supplied where a hosted zone ID is required) produced
totalRecords: 0, zonesScanned: 1 — indistinguishable from a successful scan
of a legitimately empty zone. zonesScanned now counts only zones whose
records were actually read.
Added: summary.zonesFailed: string[] lists the zone IDs whose
ListResourceRecordSets call failed, so callers can assert on read failures
instead of parsing log warnings.
Changed: When an explicit zoneFilter is given and none of its zones can
be read, list_records now throws instead of writing a zero-record success.
The error names the failed zones and reminds the caller that zoneFilter
expects hosted zone IDs, not names. A legitimately empty zone (read succeeds,
returns no records) is unaffected and still reports success. A partial failure
(some zones readable, some not) still succeeds, with the unreadable zones listed
in zonesFailed.
Upgrade note: Additive schema change. summary.zonesFailed defaults to
[], so resources stored by earlier versions still validate on read. Consumers
that computed success from zonesScanned alone should also check zonesFailed.
2026.10.14.1
Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.
Upgrade note: Metadata only. No code, schema, or behavioral changes.
2026.10.13.1
Fixed: list_zones and detect_orphans failed on current swamp with
Data name 'latest' is reserved for internal use. list_zones now writes its
zones resource as zone-scan and detect_orphans writes orphans as
orphan-scan, matching list_records' record-scan. list_records is
unchanged.
Changed: The stored data names changed. Anything that addressed the old
latest data name, for example data.latest("<model>", "latest") or
name == "latest", must use zone-scan / orphan-scan. The README query
examples named the spec (zones, orphans) rather than the data name, so they
never matched; they now use the real names. Resource specs and schemas are
unchanged, so consumers that select by spec are unaffected.
2026.09.24.1
Changed: Bump @aws-sdk/* 3.1133.0 → 3.1139.0 (3 packages)
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.11.03.1
Changed: Bump zod 4.6.5 → 4.6.7
2026.10.28.1
Fixed: list_records reported status: succeeded with zonesScanned
counting a zone even when that zone's records could not be read. A zone passed
in zoneFilter whose ListResourceRecordSets call failed (for example, a zone
name supplied where a hosted zone ID is required) produced
totalRecords: 0, zonesScanned: 1 — indistinguishable from a successful scan
of a legitimately empty zone. zonesScanned now counts only zones whose
records were actually read.
Added: summary.zonesFailed: string[] lists the zone IDs whose
ListResourceRecordSets call failed, so callers can assert on read failures
instead of parsing log warnings.
Changed: When an explicit zoneFilter is given and none of its zones can
be read, list_records now throws instead of writing a zero-record success.
The error names the failed zones and reminds the caller that zoneFilter
expects hosted zone IDs, not names. A legitimately empty zone (read succeeds,
returns no records) is unaffected and still reports success. A partial failure
(some zones readable, some not) still succeeds, with the unreadable zones listed
in zonesFailed.
Upgrade note: Additive schema change. summary.zonesFailed defaults to
[], so resources stored by earlier versions still validate on read. Consumers
that computed success from zonesScanned alone should also check zonesFailed.
2026.10.14.1
Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.
Upgrade note: Metadata only. No code, schema, or behavioral changes.
2026.10.13.1
Fixed: list_zones and detect_orphans failed on current swamp with
Data name 'latest' is reserved for internal use. list_zones now writes its
zones resource as zone-scan and detect_orphans writes orphans as
orphan-scan, matching list_records' record-scan. list_records is
unchanged.
Changed: The stored data names changed. Anything that addressed the old
latest data name, for example data.latest("<model>", "latest") or
name == "latest", must use zone-scan / orphan-scan. The README query
examples named the spec (zones, orphans) rather than the data name, so they
never matched; they now use the real names. Resource specs and schemas are
unchanged, so consumers that select by spec are unaffected.
2026.09.24.1
Changed: Bump @aws-sdk/* 3.1133.0 → 3.1139.0 (3 packages)
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.10.28.1
Fixed: list_records reported status: succeeded with zonesScanned
counting a zone even when that zone's records could not be read. A zone passed
in zoneFilter whose ListResourceRecordSets call failed (for example, a zone
name supplied where a hosted zone ID is required) produced
totalRecords: 0, zonesScanned: 1 — indistinguishable from a successful scan
of a legitimately empty zone. zonesScanned now counts only zones whose
records were actually read.
Added: summary.zonesFailed: string[] lists the zone IDs whose
ListResourceRecordSets call failed, so callers can assert on read failures
instead of parsing log warnings.
Changed: When an explicit zoneFilter is given and none of its zones can
be read, list_records now throws instead of writing a zero-record success.
The error names the failed zones and reminds the caller that zoneFilter
expects hosted zone IDs, not names. A legitimately empty zone (read succeeds,
returns no records) is unaffected and still reports success. A partial failure
(some zones readable, some not) still succeeds, with the unreadable zones listed
in zonesFailed.
Upgrade note: Additive schema change. summary.zonesFailed defaults to
[], so resources stored by earlier versions still validate on read. Consumers
that computed success from zonesScanned alone should also check zonesFailed.
2026.10.14.1
Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.
Upgrade note: Metadata only. No code, schema, or behavioral changes.
2026.10.13.1
Fixed: list_zones and detect_orphans failed on current swamp with
Data name 'latest' is reserved for internal use. list_zones now writes its
zones resource as zone-scan and detect_orphans writes orphans as
orphan-scan, matching list_records' record-scan. list_records is
unchanged.
Changed: The stored data names changed. Anything that addressed the old
latest data name, for example data.latest("<model>", "latest") or
name == "latest", must use zone-scan / orphan-scan. The README query
examples named the spec (zones, orphans) rather than the data name, so they
never matched; they now use the real names. Resource specs and schemas are
unchanged, so consumers that select by spec are unaffected.
2026.09.24.1
Changed: Bump @aws-sdk/* 3.1133.0 → 3.1139.0 (3 packages)
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.10.14.1
Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.
Upgrade note: Metadata only. No code, schema, or behavioral changes.
2026.10.13.1
Fixed: list_zones and detect_orphans failed on current swamp with
Data name 'latest' is reserved for internal use. list_zones now writes its
zones resource as zone-scan and detect_orphans writes orphans as
orphan-scan, matching list_records' record-scan. list_records is
unchanged.
Changed: The stored data names changed. Anything that addressed the old
latest data name, for example data.latest("<model>", "latest") or
name == "latest", must use zone-scan / orphan-scan. The README query
examples named the spec (zones, orphans) rather than the data name, so they
never matched; they now use the real names. Resource specs and schemas are
unchanged, so consumers that select by spec are unaffected.
2026.09.24.1
Changed: Bump @aws-sdk/* 3.1133.0 → 3.1139.0 (3 packages)
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.10.13.1
Fixed: list_zones and detect_orphans failed on current swamp with
Data name 'latest' is reserved for internal use. list_zones now writes its
zones resource as zone-scan and detect_orphans writes orphans as
orphan-scan, matching list_records' record-scan. list_records is
unchanged.
Changed: The stored data names changed. Anything that addressed the old
latest data name, for example data.latest("<model>", "latest") or
name == "latest", must use zone-scan / orphan-scan. The README query
examples named the spec (zones, orphans) rather than the data name, so they
never matched; they now use the real names. Resource specs and schemas are
unchanged, so consumers that select by spec are unaffected.
2026.09.24.1
Changed: Bump @aws-sdk/* 3.1133.0 → 3.1139.0 (3 packages)
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.09.24.1
Changed: Bump @aws-sdk/* 3.1133.0 → 3.1139.0 (3 packages)
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.09.17.1
Changed: Bump @aws-sdk/* 3.1131.0 → 3.1133.0 (3 packages)
2026.09.15.1
Changed: Bump zod 4.4.3 → 4.6.5
2026.09.14.1
Changed: Bump @aws-sdk/* 3.1126.0 → 3.1131.0 (3 packages)
2026.09.04.1
Changed: Bump @aws-sdk/* 3.1121.0 → 3.1126.0 (3 packages)
2026.08.29.1
Changed: Bump @aws-sdk/* 3.1120.0 → 3.1121.0. Dependency-only update; no schema, API, or behavioral changes.
2026.08.28.2
Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.
Upgrade note: License text only. No API, schema, or runtime behavior changed.
2026.08.28.1
Changed: Bump @aws-sdk/* 3.1114.0 → 3.1120.0 (3 packages)
2026.08.26.3
Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry
quality scorer can resolve dependencies and score the extension. An earlier
release used a bare "zod" import-map specifier, which published but scored as
unscored.
Changed: Retained explicit compilerOptions.strict in deno.json. No
behavioral or schema changes.
2026.09.15.1
Changed: Bump zod 4.4.3 → 4.6.5
2026.09.14.1
Changed: Bump @aws-sdk/* 3.1126.0 → 3.1131.0 (3 packages)
2026.09.04.1
Changed: Bump @aws-sdk/* 3.1121.0 → 3.1126.0 (3 packages)
2026.08.29.1
Changed: Bump @aws-sdk/* 3.1120.0 → 3.1121.0. Dependency-only update; no schema, API, or behavioral changes.
2026.08.28.2
Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.
Upgrade note: License text only. No API, schema, or runtime behavior changed.
2026.08.28.1
Changed: Bump @aws-sdk/* 3.1114.0 → 3.1120.0 (3 packages)
2026.08.26.3
Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry
quality scorer can resolve dependencies and score the extension. An earlier
release used a bare "zod" import-map specifier, which published but scored as
unscored.
Changed: Retained explicit compilerOptions.strict in deno.json. No
behavioral or schema changes.
2026.09.04.1
Changed: Bump @aws-sdk/* 3.1121.0 → 3.1126.0 (3 packages)
2026.08.29.1
Changed: Bump @aws-sdk/* 3.1120.0 → 3.1121.0. Dependency-only update; no schema, API, or behavioral changes.
2026.08.28.2
Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.
Upgrade note: License text only. No API, schema, or runtime behavior changed.
2026.08.28.1
Changed: Bump @aws-sdk/* 3.1114.0 → 3.1120.0 (3 packages)
2026.08.26.3
Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry
quality scorer can resolve dependencies and score the extension. An earlier
release used a bare "zod" import-map specifier, which published but scored as
unscored.
Changed: Retained explicit compilerOptions.strict in deno.json. No
behavioral or schema changes.
2026.08.29.1
Changed: Bump @aws-sdk/* 3.1120.0 → 3.1121.0. Dependency-only update; no schema, API, or behavioral changes.
2026.08.28.2
Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.
Upgrade note: License text only. No API, schema, or runtime behavior changed.
2026.08.28.1
Changed: Bump @aws-sdk/* 3.1114.0 → 3.1120.0 (3 packages)
2026.08.26.3
Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry
quality scorer can resolve dependencies and score the extension. An earlier
release used a bare "zod" import-map specifier, which published but scored as
unscored.
Changed: Retained explicit compilerOptions.strict in deno.json. No
behavioral or schema changes.
2026.08.28.2
Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.
Upgrade note: License text only. No API, schema, or runtime behavior changed.
2026.08.28.1
Changed: Bump @aws-sdk/* 3.1114.0 → 3.1120.0 (3 packages)
2026.08.26.3
Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry
quality scorer can resolve dependencies and score the extension. An earlier
release used a bare "zod" import-map specifier, which published but scored as
unscored.
Changed: Retained explicit compilerOptions.strict in deno.json. No
behavioral or schema changes.
2026.08.28.1
Changed: Bump @aws-sdk/* 3.1114.0 → 3.1120.0 (3 packages)
2026.08.26.3
Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry
quality scorer can resolve dependencies and score the extension. An earlier
release used a bare "zod" import-map specifier, which published but scored as
unscored.
Changed: Retained explicit compilerOptions.strict in deno.json. No
behavioral or schema changes.
2026.08.26.3
Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry
quality scorer can resolve dependencies and score the extension. An earlier
release used a bare "zod" import-map specifier, which published but scored as
unscored.
Changed: Retained explicit compilerOptions.strict in deno.json. No
behavioral or schema changes.
2026.08.26.1
Fixed: Added missing description field to upgrade entry for version
2026.08.24.2. The omission caused swamp extension pull to fail with a catalog
validation error ("upgrades.N.description: Invalid input: expected string,
received undefined").
2026.08.25.1
Changed: Updated labels for improved extension discoverability. Added cross-cutting category labels (security, observability, finops, infrastructure, networking, compliance, devops, ai, incident-response) where applicable.
updated labels
2026.08.24.3
Added: Output metadata attributes for observability.
durationMs: Method execution duration in milliseconds.collectedBy: Extension name that produced the data.fetchedAt: ISO 8601 timestamp when data was fetched (added to resources that previously lacked it).
2026.08.24.2
Added: Troubleshooting section documenting per-zone silent record-fetch
failures, the detect_orphans dependency on upstream data collection,
MAX_PAGES = 50 truncation behavior, Route 53 region semantics, and
false-orphan scenarios when reference data is absent.
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Docs keep secrets in a vault1/1earned
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License2/2earned
- Verified public repository2/2earned