Relationships
#403 Add a list/discover method to dbcluster for enumerating clusters in a region
Opened by jentz · 5/21/2026· Shipped 5/26/2026
The @swamp/aws/rds/dbcluster model currently exposes only single-cluster operations (create / get / update / delete / sync) — all of which require the cluster identifier to already be known. There is no way to enumerate existing clusters in the current account and region.
This is a structural gap for any audit, inventory, or migration workflow. I hit it building a "list Aurora clusters in eu-west-1 with N members" inventory for an r7g → r8g instance class cutover, and ended up writing a separate @jentz/aws-rds-inventory model to do it. Other community extensions (e.g. @webframp/aws/guardduty) ship list-style discovery methods, so the pattern is established.
Implementation scope:
- Add a
list(ordiscover) method to the dbcluster model that paginatesDescribeDBClustersand emits one data artifact per cluster. - CloudControl's
readResourcehelper isn't usable for this —AWS::RDS::DBClusterhas no CloudControl list operation — so the method needs a direct@aws-sdk/client-rdsdependency. - Reuse the existing SDK default credential chain pattern from
models/_lib/aws.ts; no new auth surface.
Related: the persisted state today is missing DBClusterMembers (filed separately). Fixing both together would make list results immediately useful for fleet operations.
Upstream repository: https://github.com/systeminit/swamp-extensions
Environment
- Extension:
@swamp/aws/rds@2026.05.06.1 - swamp:
20260520.150010.0-sha.47868db6 - OS:
darwin(aarch64) - Deno:
2.7.14+19bd3d8 - Shell:
/bin/zsh
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.