RDS Extended Support Cost Lint for Terraform
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Prices the AWS Extended Support surcharge on every RDS and Aurora database in your .tf files
Install
rds-extended-support-cost-lint file
Node 18+. The same 12 rules as the VS Code extension, from a terminal or CI.
Free
- Checks the open .tf file: every RDS and Aurora database whose engine version is billed for Extended Support today, with its yearly surcharge and the date it started.
--ruleslists every rule
With a licence ($29 once)
- Scans every .tf file in the workspace in one run and exports one Markdown report of every database's surcharge for the budget or upgrade ticket.
rds-extended-support-cost-lint --dir ./templates --report html --out report.html
One 4-vCPU instance left on MySQL 8.0 pays AWS 3,504 dollars a year in Extended Support (0.100 USD per vCPU-hour, US East).
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "rds-extended-support-cost-lint": { "command": "rds-extended-support-cost-lint", "args": ["--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: RDS Extended Support Cost Lint for Terraform
run: pip install rulestamp-rds-extended-support-cost-lint && rds-extended-support-cost-lint --dir . --ci
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install rulestamp-rds-extended-support-cost-lint
rds-extended-support-cost-lint --help
Metadata
Release files for rulestamp-rds-extended-support-cost-lint 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rulestamp_rds_extended_support_cost_lint-1.0.2.tar.gz | 16.4 kB | Without provenance | Details for rulestamp_rds_extended_support_cost_lint-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_rds_extended_support_cost_lint-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_rds_extended_support_cost_lint-1.0.2-py3-none-any.whl |
Total release size: 35.0 kB
Release files / rulestamp_rds_extended_support_cost_lint-1.0.2.tar.gz
| Download URL | rulestamp_rds_extended_support_cost_lint-1.0.2.tar.gz |
|---|---|
| Size | 16.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da779329d2dc948d0a612c1ebde239eafcafddf4e39027d2950813699ef068c8
|
|
BLAKE2b-256 checksum How to use checksums |
82f3ec714e076dc212f6da263496a4c83c7ef3bfbe2dddc035a1f41bfe28ae91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_rds_extended_support_cost_lint-1.0.2-py3-none-any.whl
| Download URL | rulestamp_rds_extended_support_cost_lint-1.0.2-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23cdcd35d51534831c11d18775f92050450c67d2620b314125c785de51a58552
|
|
BLAKE2b-256 checksum How to use checksums |
d9f556d6e4891f2b4b1b730e47632bb0522d51c87c6e19b714f82ab3f94e4b0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-rds-extended-support-cost-lint 1.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.