Aws Rds Reservations
Lists every running RDS DB instance (Aurora cluster members AND standalone single-instance RDS, via DescribeDBInstances) and every reserved DB instance (via DescribeReservedDBInstances), per profile × region — the read-only data behind reserved-instance coverage planning. Read-only (Describe* + sts:GetCallerIdentity).
A single sweep method fans out over every configured profile and region in
one execution (one model lock, all output in one pass). It emits one
instance resource per provisioned DB instance, one reserved resource per
reservation, and one scan_error per (profile, region) phase that fails — an
expired SSO token or an SCP-denied region is surfaced as a row, never
aborting the sweep. regions is required: with an empty list the sweep makes
no AWS calls and writes a single no_regions scan_error (zero data rows),
which the companion report treats as degraded rather than a healthy empty
fleet.
Pairs with the companion report @jentz/aws-rds-reservation-coverage, which
normalizes these rows into size-flexible large-equivalent units and reports
the running-minus-reserved coverage gap.
Instance-level + reservations scope. For cluster-level inventory (one
resource per Aurora / Multi-AZ DB cluster and per cluster member) see the
sibling @jentz/aws-rds-inventory.
Global Arguments
| Argument | Type | Description |
|---|---|---|
| profiles | array | Named AWS profiles to sweep, one account each. Empty (default) uses the |
| regions | array | Regions to sweep per account. Required — RDS describe calls are |
| requiredProfileSuffix | string | If set, every named profile must end with this suffix or it is refused |
Resources
Initial release. Fleet-wide RDS reserved-instance sweep across profiles x regions: one instance row per DB instance, one reserved row per reservation, and scan_error rows for failures (throttling is retried with full-jitter backoff; failures become rows rather than aborting the sweep). Malformed AWS rows are surfaced as scan_errors instead of being written as empty placeholders.
- 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
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License declared1/1earned
- Verified public repository2/2earned