cin90 aws
Keep an AWS lab account inside its budget
Cost guardrails for the labs that run in your own AWS account: a budget that actually alerts, per-lab capacity caps, a spend report, and a teardown for what the labs created.
Every subcommand refuses to touch an account listed in protected_accounts, or any account outside allowed_accounts when that list is set.
Usage
cin90 aws [command]
Flags
--all-regions work on every region enabled for the account
-h, --help help for aws
--region stringArray region to work on; repeatable, and overrides the configured regions
Commands
- cin90 aws guard: Reapply the Redshift and Glue capacity caps
- cin90 aws lab: Check a lab's resources against the instructor's checklist
- cin90 aws nuke: Tear down what the labs created
- cin90 aws prove: Capture proof that you built a lab's AWS resources
- cin90 aws selftest: Rehearse the whole prove path against a throwaway bucket (instructors)
- cin90 aws setup: Create the budget, deny policy, and scan caps (run once, on day one)
- cin90 aws status: Show spend against the budget, and what is still running
See also
Read this page in your terminal: install the cin90 CLI and run
cin90 docs. The same page is served as
raw markdown.