Skip to content

Runbooks CLI Commands Catalogยถ

Generated from runbooks --help on 2026-06-21 | runbooks v1.5.0 | 16 command groups

For functional area guidance: Start with CxO End-to-End Walkthrough (narrative) โ†’ Cloud Foundations Functional Area Runbooks (doctrine) โ†’ This page (detailed reference).


By Board-Risk Domainยถ

Domain CLI Groups Purpose See Also
1. Business Continuity inventory, cfat Org-wide backup coverage, disaster recovery Cloud Foundations ยง1
2. Operations inventory, operate, itsm Patch Manager baseline, patch compliance, change management Cloud Foundations ยง2
3. Finance finops, workspaces, validation Cost attribution, tag enforcement, optimization recommendations Cloud Foundations ยง3
4. Governance cfat, inventory, validation OU-level SCP inheritance, Config compliance, audit automation Cloud Foundations ยง4
5. Security security, cert, remediation GuardDuty 100% enrollment, compliance baselines, findings remediation Cloud Foundations ยง5
6. Infrastructure vpc, inventory, operate Network baselines, drift detection, resource provisioning Cloud Foundations ยง6

Summaryยถ

Group Commands Purpose
inventory 46 Multi-account resource discovery & enrichment (88 AWS resource types)
finops 43 Cost analysis, optimization recommendations, budget tracking
security 6 Compliance frameworks (SOC2, PCI-DSS, HIPAA, ISO27001), baselines
remediation 4 Close security findings: S3, IAM, CloudTrail, encryption
cfat 3 Cloud Foundations Assessment Tool maturity scoring
vpc 7 Network architecture validation, flow logs, cost optimization
validation 8 Cross-validation gates, accuracy benchmarking
cert 5 Certificate discovery & expiry monitoring
operate 5 Resource operations: EC2 start/stop, S3 provisioning, IaC deploy
itsm (see inventory) ITSM integration (change records, incidents)
workspaces (see finops) WorkSpaces cost analysis & decommission scoring
csdm internal CMDB/CSDM exports (ServiceNow integration prep)
orr internal Organization resources registry
cloudops internal Platform team utilities
common internal Shared CLI infrastructure
mcp internal MCP server integration

Commands by Groupยถ

finopsยถ

Usage: runbooks finops [OPTIONS] COMMAND [ARGS]...

  Financial operations and cost optimization for AWS resources.

  Comprehensive cost analysis, budget management, and financial reporting with
  multi-format export capabilities.

  Features: โ€ข Real-time cost analysis with MCP validation โ€ข Multi-format exports:
  CSV, JSON, PDF, Markdown โ€ข Quarterly intelligence with strategic financial
  reporting โ€ข Enterprise AWS profile support with multi-account capabilities

  Examples:     runbooks finops dashboard --profile billing-profile
  runbooks finops dashboard --all-profiles --timeframe monthly     runbooks
  finops dashboard --regions ap-southeast-2 ap-southeast-6     runbooks finops
  export --format pdf --output-dir ./reports

Options:
  --tags TEXT                     Filter by tags (key=value format)
  --accounts TEXT                 Filter by specific account IDs
  --all                           Multi-account discovery
                                  (CENTRALISED_OPS_PROFILE as aggregator).

                                  ๐Ÿ“‹ Behavior: โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”
                                  โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

                                  โ€ข Queries AWS Resource Explorer aggregator
                                  index โ€ข Discovers resources across ALL
                                  accounts in Landing Zone โ€ข Requires
                                  CENTRALISED_OPS_PROFILE with cross-account
                                  permissions

                                  ๐Ÿ” Enrichment Layers (Automatic):   โ€ข
                                  Organizations metadata: MANAGEMENT_PROFILE
                                  โ€ข Cost data: BILLING_PROFILE   Note:
                                  Enrichment uses separate profiles regardless
                                  of discovery mode

                                  Use Case: Enterprise platform teams managing
                                  67+ account Landing Zones
  --profiles TEXT                 Specific AWS profiles (comma-separated,
                                  e.g., "billing,security,audit")
  --regions TEXT                  Specific AWS regions (space-separated)
  --all-regions                   Process all enabled AWS regions
  -f, --format, --output-format [json|csv|table|pdf|markdown]
                                  Output format for results display
                                  (-f/--format preferred, --output-format
                                  legacy)
  --output-dir PATH               Directory for generated files and evidence
                                  packages
  --all-outputs                   Generate all output formats (JSON, CSV, PDF,
                                  Markdown) - use with --output-dir
  --csv                           Export to CSV format (convenience flag,
                                  activates --all-outputs)
  --json                          Export to JSON format (convenience flag,
                                  activates --all-outputs)
  --markdown                      Export to Markdown format (convenience flag,
                                  activates --all-outputs)
  --profile TEXT                  AWS profile for single-account operations.

                                  ๐Ÿ“‹ Profile Selection Guide: โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”
                                  โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

                                  Single Account โ†’ Use --profile YOUR_PROFILE
                                  Example: --profile dev-account   When:
                                  Developer/operator working in one AWS
                                  account

                                  Multi-Account LZ โ†’ Use --all-profiles (see
                                  inventory commands)   Example: --all-
                                  profiles   When: Platform team discovering
                                  across organization

                                  ๐Ÿ” Enrichment Profiles (Automatic):   โ€ข
                                  Organizations: MANAGEMENT_PROFILE   โ€ข Costs:
                                  BILLING_PROFILE   Note: Separate from
                                  discovery profile

                                  Decision: Single account = --profile |
                                  Multi-account = --all-profiles
  --region TEXT                   AWS region override (default: ap-
                                  southeast-2)
  --dry-run                       Safe analysis mode - no resource
                                  modifications (enterprise default)
  --help                          Show this message and exit.

Commands:
  analyze-ec2                     EC2 cost analysis with 4-way enrichment.
  analyze-graviton-eligibility    Graviton migration eligibility...
  analyze-s3-storage-lens         Analyze S3 Storage Lens metrics for...
  analyze-workspaces              WorkSpaces cost analysis with...
  appstream-decommission-analysis
                                  AppStream decommission analysis with...
  azure                           Azure Cost Management analysis.
    azure anomaly                 Detect cost anomalies (spending spikes).
    azure daily                   Daily cost breakdown by Azure service.
    azure monthly                 Monthly cost summary with subscription breakdown.
    azure preflight               Pre-flight auth and access validation for Azure FinOps.
    azure validate                Validate SDK against Azure native API (ground truth).
  check-config-compliance         Check AWS Config compliance and map...
  cost-drops                      Detect month-over-month cost drops...
  dashboard                       Multi-account cost visibility with...
  detect-orphans                  Detect orphaned AWS resources across...
  detect-rds-idle                 Detect idle RDS instances for $50K...
  ec2-decommission-analysis       EC2 decommission analysis with E1-E7...
  ec2-snapshots                   EC2 snapshot cost optimization and...
  enrich-workspaces               Enrich WorkSpaces inventory with...
  export                          Export financial analysis results in...
  infrastructure                  Infrastructure cost optimization analysis
    infrastructure analyze        Comprehensive infrastructure optimization analysis
    infrastructure elastic-ip     Elastic IP cost optimization analysis
    infrastructure load-balancer  Load Balancer cost optimization analysis
    infrastructure nat-gateway    NAT Gateway cost optimization analysis
    infrastructure vpc-endpoint   VPC Endpoint cost optimization analysis
  lambda-analysis                 Lambda cost and activity analysis...
  optimize                        Generate cost optimization...
  optimize-cloudwatch-costs       Analyze and optimize CloudWatch log...
  optimize-s3-lifecycle           S3 Lifecycle Optimizer - Automated...
  optimize-savings-plans          Generate hybrid Savings Plans + RI...
  scenario                        Execute a FinOps business scenario...
  sprint1                         Run Sprint 1 cost optimization analysis.
  validate                        4-Way Validation: HTML vs CSV vs MCP...
  validate-with-mcp               Validate runbooks cost projections...
  vizro                           Launch interactive Vizro FinOps...
  workspaces-decommission-analysis
                                  WorkSpaces decommission analysis with...

inventoryยถ

Runbooks Inventory - Multi-account AWS resource discovery

๐Ÿ“‹ Command Categories (40 operations across 9 categories):
1๏ธโƒฃ  Discovery: resource-explorer (88 AWS resource types)
2๏ธโƒฃ  Organizations: org-*, accounts-* (multi-account management)
3๏ธโƒฃ  VPC/Network: vpc-*, nat-*, elb-* (network architecture)
4๏ธโƒฃ  CloudFormation: cfn-*, stack-* (IaC drift detection)
5๏ธโƒฃ  Activity/Scoring: enrich-*, score-* (decommission analysis)
6๏ธโƒฃ  Security/Compliance: security-*, audit-*, check-*
7๏ธโƒฃ  Workflows: workflow-*, pipeline-* (automated pipelines)
8๏ธโƒฃ  Validation: validate-*, verify-* (MCP cross-validation)
9๏ธโƒฃ  Utilities: export-*, clean-*, show-* (helper commands)

Inventory Commands (46 commands)
Commands (46):
  collect                        Multi-account resource discovery via Resource Explorer
  resource-explorer              Discover resources by friendly alias (88 types)
  resource-types                 List all 88 supported resource types
  discover-rds                   RDS database discovery
  discover-lambda                Lambda function discovery
  workspaces                     WorkSpaces discovery (6-phase investigation)
  collect-containers             Container discovery (ECS clusters, tasks, services)
  list-org-accounts              List AWS accounts in organization
  list-org-users                 List IAM users across organization
  draw-org                       Visualize organization hierarchy
  check-landingzone              Validate Landing Zone configuration
  check-controltower             Validate Control Tower setup
  find-lz-versions               Discover Landing Zone versions
  collect-ram-shares             Discover AWS RAM shares
  enrich-accounts                Add Organizations metadata
  enrich-costs                   Add cost data from Cost Explorer
  enrich-activity                Add CloudTrail activity signals
  enrich-ec2                     EC2-specific enrichment (now includes SSM columns)
  score-decommission             Score decommission candidates (E1-E8/W1-W6, now includes SSM heartbeat)
  vpc flow-logs                  VPC Flow Logs discovery and analysis
  vpc nat-traffic                NAT Gateway traffic analysis
  vpc security-groups            Security group validation
  vpc validate                   VPC architecture assessment
  vpc dependencies               Cross-VPC dependency analysis
  list-elbs                      Load balancer discovery (ELB/ALB/NLB)
  list-enis                      Network interface discovery (ENI) with optional instance filter
  ssm-status                     SSM agent health and patch compliance per instance
  ebs-health                     EBS volume layout and IOPS utilization per instance
  find-cfn-drift                 CloudFormation drift detection
  find-cfn-orphaned-stacks       Orphaned stack discovery
  list-cfn-stacks                List CloudFormation stacks
  list-cfn-stacksets             List CloudFormation StackSets
  find-cfn-stackset-drift        StackSet drift detection
  recover-cfn-stack-ids          Recover CloudFormation stack IDs
  check-cloudtrail-compliance    CloudTrail compliance validation
  list-guardduty-detectors       GuardDuty detector discovery
  tag-coverage                   Tag coverage analysis
  drift-detection                Comprehensive drift detection
  list-sns-topics                SNS topic discovery
  collect-messaging              Messaging resources (SQS queues, SNS topics)
  collect-analytics              Analytics resources (Athena, Glue databases/tables)
  workflow-single-account        4-layer pipeline (single account)
  workflow-multi-account         5-layer pipeline (multi-account LZ)
  pipeline-summary               Display pipeline execution summary
  validate-mcp                   MCP cross-validation
  validate-costs                 Cost data accuracy validation
  cross-validate                 4-way cross-validation (MCP/CLI/Console/AWS)
  clean-outputs                  Clean output directory

๐Ÿ’ก Usage: runbooks inventory [COMMAND] [OPTIONS]
๐Ÿ“– Example: runbooks inventory resource-explorer --resource-type ec2 --profile ops --output /tmp/ec2.csv


๐Ÿ“‹ Taskfile Operations Available:
Runbooks - Inventory Module Operations
โ”œโ”€โ”€ Discovery Operations (6 operations)
โ”‚   โ””โ”€โ”€ โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚       โ”‚ Task Name                           โ”‚ Description                                                  โ”‚
โ”‚       โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚       โ”‚ ๐Ÿ”„ discover-ec2                     โ”‚ Discover EC2 instances across organization (Universal)       โ”‚
โ”‚       โ”‚ ๐Ÿ”„ discover-rds                     โ”‚ Discover RDS databases across organization (Universal)       โ”‚
โ”‚       โ”‚ ๐Ÿ”„ discover-s3                      โ”‚ Discover S3 buckets across organization (Universal)          โ”‚
โ”‚       โ”‚ ๐Ÿ”„ discover-lambda                  โ”‚ Discover Lambda functions across organization (Universal)    โ”‚
โ”‚       โ”‚ ๐Ÿ”„ workspaces                       โ”‚ WorkSpaces investigation (6-phase analysis)                  โ”‚
โ”‚       โ”‚ ๐Ÿ”„ list-resource-types              โ”‚ List all available resource types for discovery (Universal)  โ”‚
โ”‚       โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
โ”œโ”€โ”€ Organizations Operations (6 operations)
โ”‚   โ””โ”€โ”€ โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚       โ”‚ Task Name                           โ”‚ Description                                                  โ”‚
โ”‚       โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚       โ”‚ ๐Ÿข list-accounts                    โ”‚ List all AWS accounts in organization (Multi-Account LZ)     โ”‚
โ”‚       โ”‚ ๐Ÿข draw-org                         โ”‚ Visualize AWS Organizations hierarchy (Multi-Account LZ)     โ”‚
โ”‚       โ”‚ ๐Ÿข check-landing-zone               โ”‚ Validate AWS Landing Zone configuration (Multi-Account LZ)   โ”‚
โ”‚       โ”‚ ๐Ÿข check-control-tower              โ”‚ Validate AWS Control Tower setup (Multi-Account LZ)          โ”‚
โ”‚       โ”‚ ๐Ÿข list-org-users                   โ”‚ List all IAM users across AWS organization accounts          โ”‚
โ”‚       โ”‚                                     โ”‚ (Multi-Account LZ)                                           โ”‚
โ”‚       โ”‚ ๐Ÿข find-lz-versions                 โ”‚ Discover AWS Landing Zone versions across organization       โ”‚
โ”‚       โ”‚                                     โ”‚ (Multi-Account LZ)                                           โ”‚
โ”‚       โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
โ”œโ”€โ”€ Cost & Account Enrichment (2 operations)
โ”‚   โ””โ”€โ”€ โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚       โ”‚ Task Name                           โ”‚ Description                                                  โ”‚
โ”‚       โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚       โ”‚ โš™๏ธ enrich-accounts                  โ”‚ Enrich resources with AWS Organizations account metadata     โ”‚
โ”‚       โ”‚                                     โ”‚ (renamed from enrich-organizations) (Context-Dependent)      โ”‚
โ”‚       โ”‚ ๐Ÿ”„ enrich-costs                     โ”‚ Add cost data to discovered resources (Universal)            โ”‚
โ”‚       โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
โ”œโ”€โ”€ Activity & Scoring Operations (3 operations)
โ”‚   โ””โ”€โ”€ โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚       โ”‚ Task Name                           โ”‚ Description                                                  โ”‚
โ”‚       โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚       โ”‚ ๐Ÿ”„ enrich-activity                  โ”‚ Add activity metrics to resources (Universal)                โ”‚
โ”‚       โ”‚ ๐Ÿ”„ enrich-ec2                       โ”‚ EC2-specific enrichment with detailed instance metadata      โ”‚
โ”‚       โ”‚                                     โ”‚ (Universal)                                                  โ”‚
โ”‚       โ”‚ ๐Ÿ”„ score-decommission               โ”‚ Calculate decommission scores for resources (Universal)      โ”‚
โ”‚       โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
โ”œโ”€โ”€ Pipeline Operations (3 operations)
โ”‚   โ””โ”€โ”€ โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚       โ”‚ Task Name                           โ”‚ Description                                                  โ”‚
โ”‚       โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚       โ”‚ ๐Ÿ”„ pipeline-5-layer                 โ”‚ Execute complete 5-layer enrichment pipeline (EC2)           โ”‚
โ”‚       โ”‚                                     โ”‚ (Universal)                                                  โ”‚
โ”‚       โ”‚ ๐Ÿ”„ pipeline-5-layer-workspaces      โ”‚ Execute complete 5-layer enrichment pipeline (WorkSpaces)    โ”‚
โ”‚       โ”‚                                     โ”‚ (Universal)                                                  โ”‚
โ”‚       โ”‚ ๐Ÿ”„ pipeline-summary                 โ”‚ Display pipeline execution summary (Universal)               โ”‚
โ”‚       โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
โ”œโ”€โ”€ Validation Operations (2 operations)
โ”‚   โ””โ”€โ”€ โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚       โ”‚ Task Name                           โ”‚ Description                                                  โ”‚
โ”‚       โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚       โ”‚ ๐Ÿ”„ validate-mcp                     โ”‚ MCP cross-validation (Universal)                             โ”‚
โ”‚       โ”‚ ๐Ÿ”„ validate-costs                   โ”‚ Validate cost data accuracy against AWS Cost Explorer        โ”‚
โ”‚       โ”‚                                     โ”‚ (Universal)                                                  โ”‚
โ”‚       โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
โ”œโ”€โ”€ Workflow Templates (2 operations)
โ”‚   โ””โ”€โ”€ โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚       โ”‚ Task Name                           โ”‚ Description                                                  โ”‚
โ”‚       โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚       โ”‚ ๐Ÿ“‹ workflow-single-account          โ”‚ Best practice workflow for single AWS account (4-layer       โ”‚
โ”‚       โ”‚                                     โ”‚ pipeline) (Workflow)                                         โ”‚
โ”‚       โ”‚ ๐Ÿ“‹ workflow-multi-account           โ”‚ Best practice workflow for multi-account Landing Zone        โ”‚
โ”‚       โ”‚                                     โ”‚ (5-layer pipeline) (Workflow)                                โ”‚
โ”‚       โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
โ”œโ”€โ”€ Utility Operations (1 operations)
โ”‚   โ””โ”€โ”€ โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚       โ”‚ Task Name                           โ”‚ Description                                                  โ”‚
โ”‚       โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚       โ”‚ ๐Ÿ› ๏ธ clean-outputs                    โ”‚ Clean output directory (Utility)                             โ”‚
โ”‚       โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
โ””โ”€โ”€ โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ Summary & Legend โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
    โ”‚ Total Operations: 33                                                                                             โ”‚
    โ”‚ Categorized: 25                                                                                                  โ”‚
    โ”‚ Uncategorized: 8                                                                                                 โ”‚
    โ”‚                                                                                                                  โ”‚
    โ”‚ Context Legend:                                                                                                  โ”‚
    โ”‚ ๐Ÿข Multi-Account LZ (6)  ๐Ÿ”„ Universal (23)                                                                       โ”‚
    โ”‚ โš™๏ธ Context-Dependent (1)  ๐Ÿ“‹ Workflow (2)  ๐Ÿ› ๏ธ Utility (1)                                                        โ”‚
    โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ

securityยถ

Security Commands (7 commands)
Commands (7):
  assess                         Multi-framework compliance assessment (SOC2, PCI-DSS, HIPAA, ISO27001) with optional resource-id filter
  baseline                       Security baseline validation with remediation recommendations
  report                         Generate compliance reports (PDF, HTML, Markdown, JSON)
  remediate-findings             Remediate Security Hub findings across multi-account organization (FIN-63/62/61)
  deploy-guardduty               Deploy GuardDuty organization-wide with delegated admin configuration (FIN-64)
  cert-inventory                 Multi-cloud certificate inventory (ACM, IAM, Key Vault) with expiry dashboard
  host-findings                  SecurityHub + GuardDuty + Inspector findings for a specific resource

vpcยถ

VPC Commands (8 commands)
Commands (8):
  analyze                        Comprehensive VPC analysis with cost optimization (now with instance-ip filter)
  analyze-endpoint-activity      Analyze VPC endpoint activity via CloudTrail (90-day lookback).
  topology                       Network topology discovery and visualization
  network-discover               Multi-account network discovery with diagrams
  discover-firewall-bypass       Security group firewall bypass detection
  nat-gateway                    NAT Gateway cost optimization
  vpce-cleanup                   VPC Endpoint cleanup and cost reduction
  flow-log-query                 CloudWatch Logs Insights query for VPC flow logs (per IP, 7-day default)

operateยถ

Operate Commands (4 sub-groups, 5 commands)
Commands (5):
  ec2 start                      Start EC2 instances (reduce idle time, optimize availability)
  ec2 stop                       Stop EC2 instances (cost savings, schedule optimization)
  s3 create-bucket               Create S3 buckets (secure, compliant, encrypted)
  vpc create-vpc                 Create VPCs (network isolation, multi-tier architecture)
  cloudformation deploy          Deploy CloudFormation stacks (IaC automation, repeatable deployments)

certยถ

Certificate Commands (5 commands)
Commands (5):
  inventory                      Discover certificates across AWS accounts and Azure subscriptions
  expiring                       Show certificates expiring within N days (default: 30)
  dns-check                      Check ACM DNS validation CNAME records via dig
  report                         Generate executive certificate assessment report (Markdown)
  triage                         Combined triage: inventory + expiring + executive report

cfatยถ

Cloud Foundations Assessment Tool โ€” CFAT Commands (3 commands)
Commands (3):
  assess                         Comprehensive framework assessment
  review                         Structured architecture review
  report                         Generate assessment reports

remediationยถ

Remediation Commands (4 commands)
Commands (4):
  s3-security                    S3 security remediation (block public access, enforce SSL, enable encryption)
  list-accounts                  List available accounts for remediation operations
  config-info                    Display current remediation configuration and environment setup
  generate-config                Generate universal configuration templates for remediation operations

validationยถ

Validation Commands (8 commands)
Commands (8):
  validate-all                   Run all validation operations
  costs                          Validate Cost Explorer data accuracy
  organizations                  Validate Organizations API accuracy
  single                         Validate single operation (costs, organizations, ec2, security, vpc)
  benchmark                      Performance benchmarking (iterations, accuracy targets)
  test                           Comprehensive test framework (Sprint 1 validation)
  status                         Framework status and health check
  sync-check                     Detect notebooks that break after CLI command changes.

Command Details โ€” Core Operationsยถ

inventory ssm-statusยถ

Purpose: SSM agent health, patch compliance, and recent command invocations per EC2 instance.

Usage:

runbooks inventory ssm-status --instance-id i-0123456789abcdef0 --profile ops

Options: - --instance-id (required): EC2 instance ID (e.g., i-0123456789abcdef0) - --profile (optional): AWS profile for authentication (default: default)

Output: 3-section Rich table display: 1. Agent Info: Agent version, ping status, last ping time, activation code 2. Patch Compliance: Patch manager status, compliant/non-compliant counts, last scan 3. Recent Commands: Last 5 command invocations (document ID, status, execution time, command output)

Example Output:

SSM Agent Status: i-0123456789abcdef0
โ”œโ”€ Agent Version: 3.2.1234.0
โ”œโ”€ Ping Status: Online
โ”œโ”€ Last Ping: 2026-04-10T14:23:45Z
โ””โ”€ Activation Code: (redacted)

Patch Compliance
โ”œโ”€ Manager: ENABLED
โ”œโ”€ Compliant: 156 patches
โ”œโ”€ Non-Compliant: 3 patches (updates pending)
โ””โ”€ Last Scan: 2026-04-10T02:00:00Z

Recent Commands (last 5)
โ”œโ”€ ssm-command-12345abc: SUCCESS (2026-04-10T14:15:22Z)
โ”œโ”€ ssm-command-12345abd: SUCCESS (2026-04-09T22:30:11Z)
โ””โ”€ ...


inventory ebs-healthยถ

Purpose: EBS volume layout, IOPS utilization (30-day average), and encryption audit per EC2 instance.

Usage:

runbooks inventory ebs-health --instance-id i-0123456789abcdef0 --profile ops

Options: - --instance-id (required): EC2 instance ID - --profile (optional): AWS profile for authentication

Output: Rich table with summary panel:

Volume ID Device Size (GB) Type IOPS Throughput (MiB/s) Encrypted KMS Key
vol-abc123 /dev/xvda 100 gp3 4000 250 Yes arn:aws:kms:...
vol-def456 /dev/xvdb 500 io2 6400 1000 Yes arn:aws:kms:...

Summary Panel: - Total capacity: 600 GB - 30-day IOPS avg: ~3200 IOPS - Encryption: 2/2 volumes encrypted (100%) - Optimization tip: (e.g., gp3 IOPS below 3000 โ€” consider reducing)


vpc flow-log-queryยถ

Purpose: CloudWatch Logs Insights query for VPC Flow Logs filtered to a specific private IP address. Returns source/destination traffic, protocol analysis, and flow classification.

Usage:

runbooks vpc flow-log-query --instance-ip 10.1.2.3 --vpc-id vpc-abc123def --days 7 --profile ops

Options: - --instance-ip (required): Private IP address (e.g., 10.1.2.3) - --vpc-id (required): VPC ID (e.g., vpc-abc123def) - --days (optional, default 7): Query period in days - --profile (optional): AWS profile

Output: Rich table with traffic classification:

Source IP Dest IP Sport Dport Protocol Bytes Packets Flow Count Classification
10.1.2.3 10.2.3.4 49521 443 TCP 524288 1024 142 HTTPS (Egress)
10.1.2.3 8.8.8.8 53401 53 UDP 4096 8 8 DNS Query

Traffic Classification Legend: - HTTP/HTTPS (80, 443) - DNS (53, 5353) - SSH (22) - RDP (3389) - Internal (RFC 1918 targets) - External (public IPs) - Unknown (unclassified ports)


security host-findingsยถ

Purpose: Aggregated security findings from SecurityHub, GuardDuty, and Inspector for a specific resource (EC2 instance or resource ARN). Organized by severity and finding source.

Usage:

runbooks security host-findings --resource-id i-0123456789abcdef0 --profile ops

Options: - --resource-id (required): Instance ID (i-xxx) or full resource ARN - --profile (optional): AWS profile

Output: Findings organized by severity, then by source (SecurityHub | GuardDuty | Inspector):

CRITICAL Findings (2) - SecurityHub: "EC2.19 - Security group allows unrestricted ingress to port 22" (Risk: SSH brute-force) - GuardDuty: "Trojan.EC2/DNSDataExfiltration.C" (Risk: DNS exfiltration detected)

HIGH Findings (5) - Inspector: "CVE-2024-1234 - OpenSSL 1.0.2 EOL" (CVSS 8.2) - SecurityHub: "CloudTrail API logging is disabled" (Compliance: PCI-DSS 10.1)

MEDIUM Findings (8) - (list continues...)

Summary Panel:

Total Findings: 15
โ”œโ”€ CRITICAL:   2
โ”œโ”€ HIGH:       5
โ”œโ”€ MEDIUM:     8
โ””โ”€ LOW:        0

Recommended Actions:
1. Close SSH security group rule (54 days open)
2. Apply OS patches (CVE-2024-1234)
3. Enable CloudTrail logging


Enhanced Commands โ€” SSM & EBS Enrichmentยถ

inventory enrich-ec2 (updated)ยถ

New columns added: - ssm_agent_status: Online/Offline (from Systems Manager) - ssm_ping_status: Last ping timestamp - last_patch_scan: Date of last patch manager scan - patch_non_compliant_count: Number of pending patches

Usage:

runbooks inventory enrich-ec2 --profile ops --output /tmp/ec2-enriched.csv


inventory list-enis (updated)ยถ

New filter option: - --instance-id: Filter ENIs by EC2 instance ID

Usage:

runbooks inventory list-enis --instance-id i-0123456789abcdef0 --profile ops


security assess (updated)ยถ

New filter option: - --resource-id: Filter findings to a specific resource (instance ID or ARN)

Usage:

runbooks security assess --resource-id i-0123456789abcdef0 --framework pci-dss


vpc analyze (updated)ยถ

New filter option: - --instance-ip: Filter traffic analysis to a specific private IP address

Usage:

runbooks vpc analyze --instance-ip 10.1.2.3 --vpc-id vpc-abc123def


inventory score-decommission (updated)ยถ

New signal (E8): - SSM Heartbeat: 5 points if no SSM ping in 30 days - Decommission candidates now scored as E1-E8 (previously E1-E7)

Signal Summary: - E1: No CloudTrail activity (30 days) โ€” 10 pts - E2: No VPC Flow Logs activity (30 days) โ€” 10 pts - E3: Zero CPU utilization (30 days) โ€” 8 pts - E4: Zero network I/O (30 days) โ€” 8 pts - E5: Instance stopped (>60 days) โ€” 5 pts - E6: Orphaned ENI (no attachment) โ€” 3 pts - E7: No tags/cost allocation โ€” 2 pts - E8: No SSM heartbeat (30 days) โ€” 5 pts [NEW]

Decommission Score Tiers: - โ‰ฅ40 pts: Ready for decommission (executive review) - 30-39 pts: Review recommended (operations team) - <30 pts: Monitor (no action)


Investigation Orchestratorsยถ

inventory ec2-investigateยถ

Purpose: 6-phase EC2 host investigation orchestrator. Chains multiple operations (EC2 enrichment, EBS health, security findings, network flow logs, SSM status, risk scoring) into a single unified report with prioritized recommendations.

Usage:

runbooks inventory ec2-investigate --instance-id i-0123456789abcdef0 --profile ops
runbooks inventory ec2-investigate --instance-id i-0123456789abcdef0 --profile ops --output json

Options: - --instance-id (required): EC2 instance ID (e.g., i-0123456789abcdef0) - --profile (optional): AWS profile for authentication (default: default) - --output (optional): json for structured JSON output (default: Rich panel display)

Phases: 1. Discovery: Fetch EC2 instance metadata (type, state, security groups, VPC, subnets) 2. EBS Health: Volume layout, IOPS utilization, encryption audit 3. Security Findings: Aggregated findings from SecurityHub, GuardDuty, Inspector 4. Network Analysis: VPC Flow Logs traffic classification (if private IP present) 5. SSM Status: Agent health, patch compliance, recent command history 6. Risk Scoring: Combined risk score (0-100) with prioritized remediation steps

Output: Rich multi-section panel:

EC2 Investigation Report: i-0123456789abcdef0
โ”œโ”€ Instance: t3.large | Running | VPC: vpc-abc123 | AZ: ap-southeast-2a
โ”œโ”€
โ”œโ”€ EBS Storage (3 volumes)
โ”‚  โ”œโ”€ /dev/xvda: vol-abc123 (100 GB, gp3, 4000 IOPS) โœ“ Encrypted
โ”‚  โ”œโ”€ /dev/xvdb: vol-def456 (500 GB, io2, 6400 IOPS) โœ“ Encrypted
โ”‚  โ””โ”€ Total Capacity: 600 GB | 30-day IOPS avg: 3200 | Encryption: 100%
โ”œโ”€
โ”œโ”€ Security Findings: 7 total
โ”‚  โ”œโ”€ CRITICAL (2): Security group unrestricted SSH, DNS exfiltration detected
โ”‚  โ””โ”€ HIGH (5): EOL patches (CVE-2024-1234), CloudTrail disabled
โ”œโ”€
โ”œโ”€ Network Activity (last 7 days)
โ”‚  โ”œโ”€ Outbound HTTPS: 524 MB (142 flows)
โ”‚  โ”œโ”€ Inbound SSH: 2 MB (8 flows)
โ”‚  โ””โ”€ DNS: 4 MB (8 queries)
โ”œโ”€
โ”œโ”€ SSM Agent: Online (v3.2.1234) | Patches: 3 non-compliant | Scanned: 2026-04-10
โ”œโ”€
โ””โ”€ RISK SCORE: 72/100 [HIGH]
   1. Close SSH security group rule (54 days open)
   2. Apply pending OS patches (CVE-2024-1234)
   3. Enable CloudTrail logging

inventory rds-investigateยถ

Purpose: 6-phase RDS database investigation orchestrator. Chains RDS discovery, metadata enrichment, security assessment, network analysis, compliance checks, and risk scoring into a unified report.

Usage:

runbooks inventory rds-investigate --db-instance-id prod-postgres-01 --profile ops
runbooks inventory rds-investigate --db-instance-id prod-postgres-01 --profile ops --output json

Options: - --db-instance-id (required): RDS DB instance identifier (e.g., prod-postgres-01) - --profile (optional): AWS profile for authentication - --output (optional): json for structured JSON output

Phases: 1. Discovery: DB engine, version, instance class, Multi-AZ status, backup retention 2. Metadata: Storage allocation, parameter groups, option groups, performance insights 3. Security: Encryption (KMS key), IAM auth, security groups, network exposure 4. Network: VPC/subnet configuration, publicly accessible flag, security group rules 5. Compliance: Automated backups, backup window, copy-on-write, deletion protection 6. Risk Scoring: Combined risk score (0-100) with recommendations

Output: Rich multi-section panel:

RDS Investigation Report: prod-postgres-01
โ”œโ”€ Database: PostgreSQL 14.7 | db.r6g.xlarge | Multi-AZ: Yes | Backup: 7 days
โ”œโ”€
โ”œโ”€ Storage & Performance
โ”‚  โ”œโ”€ Allocated: 1000 GB (gp3)
โ”‚  โ”œโ”€ IOPS: 3000 provisioned
โ”‚  โ”œโ”€ Performance Insights: Enabled
โ”‚  โ””โ”€ Enhanced Monitoring: Enabled (1-minute granularity)
โ”œโ”€
โ”œโ”€ Security Posture
โ”‚  โ”œโ”€ Encryption at Rest: โœ“ Yes (KMS key: arn:aws:kms:...)
โ”‚  โ”œโ”€ Encryption in Transit: โœ“ Yes (SSL/TLS enforced)
โ”‚  โ”œโ”€ IAM Authentication: โœ“ Enabled
โ”‚  โ”œโ”€ Public Access: โœ— NO (secure)
โ”‚  โ””โ”€ Security Groups: 2 rules (port 5432, restricted CIDR)
โ”œโ”€
โ”œโ”€ Compliance & Backup
โ”‚  โ”œโ”€ Automated Backups: Enabled (7-day retention)
โ”‚  โ”œโ”€ Backup Window: 23:00-23:30 UTC
โ”‚  โ”œโ”€ Copy-on-Write: Enabled (cross-region replication)
โ”‚  โ””โ”€ Deletion Protection: Enabled
โ”œโ”€
โ””โ”€ RISK SCORE: 15/100 [LOW]
   Configuration follows AWS best practices. Monitor: parameter group changes, backup timing.

inventory s3-investigateยถ

Purpose: 6-phase S3 bucket investigation orchestrator. Audits bucket configuration, public access, encryption, versioning, logging, compliance, and risk scoring.

Usage:

runbooks inventory s3-investigate --bucket-name prod-app-data --profile ops
runbooks inventory s3-investigate --bucket-name prod-app-data --profile ops --output json

Options: - --bucket-name (required): S3 bucket name (e.g., prod-app-data) - --profile (optional): AWS profile for authentication - --output (optional): json for structured JSON output

Phases: 1. Discovery: Bucket location, creation date, versioning status, object count 2. Metadata: ACLs, bucket policies, access control lists, object tagging 3. Security: Block public access settings, encryption (SSE-S3/SSE-KMS/DSSE), CORS policies 4. Network: VPC endpoints, transfer acceleration, CloudFront distribution associations 5. Compliance: Logging (CloudTrail, server-access logs), lifecycle policies, MFA delete 6. Risk Scoring: Combined risk score (0-100) with recommendations

Output: Rich multi-section panel:

S3 Investigation Report: prod-app-data
โ”œโ”€ Bucket: prod-app-data | Region: ap-southeast-2 | Created: 2023-01-15
โ”œโ”€
โ”œโ”€ Storage & Objects
โ”‚  โ”œโ”€ Total Objects: 2,487,365
โ”‚  โ”œโ”€ Total Size: 4.2 TB
โ”‚  โ”œโ”€ Versioning: Enabled (1.1 TB in previous versions)
โ”‚  โ””โ”€ Object Lock: Not configured
โ”œโ”€
โ”œโ”€ Public Access Assessment
โ”‚  โ”œโ”€ Block Public ACLs: โœ“ YES
โ”‚  โ”œโ”€ Ignore Public ACLs: โœ“ YES
โ”‚  โ”œโ”€ Block Public Policy: โœ“ YES
โ”‚  โ”œโ”€ Restrict Public Buckets: โœ“ YES
โ”‚  โ””โ”€ Public Objects Detected: 0
โ”œโ”€
โ”œโ”€ Encryption & Protection
โ”‚  โ”œโ”€ Default Encryption: โœ“ Yes (SSE-KMS, key: arn:aws:kms:...)
โ”‚  โ”œโ”€ Bucket Key: โœ“ Enabled (cost optimization)
โ”‚  โ”œโ”€ Lifecycle Expiration: โœ“ Configured (90-day cleanup)
โ”‚  โ””โ”€ Server-Access Logging: โœ“ Enabled (target: access-logs bucket)
โ”œโ”€
โ”œโ”€ Compliance & Monitoring
โ”‚  โ”œโ”€ CloudTrail Data Events: โœ“ Enabled
โ”‚  โ”œโ”€ CloudWatch Alarms: โœ“ 3 configured (size, deletion, policy change)
โ”‚  โ”œโ”€ Replication: Not configured
โ”‚  โ””โ”€ Transfer Acceleration: Disabled
โ”œโ”€
โ””โ”€ RISK SCORE: 8/100 [LOW]
   Bucket is well-secured with all recommended protections enabled.
   Recommendation: Enable cross-region replication for DR (optional).

inventory workspaces-investigateยถ

Purpose: 6-phase Amazon WorkSpaces investigation orchestrator. Audits WorkSpace configuration, cost optimization, user activity, compliance, security, and risk scoring.

Usage:

runbooks inventory workspaces-investigate --workspace-id ws-0123456789abcdef0 --profile ops
runbooks inventory workspaces-investigate --workspace-id ws-0123456789abcdef0 --profile ops --output json

Options: - --workspace-id (required): WorkSpaces workspace ID (e.g., ws-0123456789abcdef0) - --profile (optional): AWS profile for authentication - --output (optional): json for structured JSON output

Phases: 1. Discovery: User, bundle type, directory, state, creation date, last connection 2. Metadata: IP address, root volume size, user volume size, running mode 3. Security: User account status, MFA enabled, Active Directory integration 4. Network: VPC, subnet, security group rules, ENI configuration 5. Compliance: Encryption (root & user volumes), backup settings, tagging 6. Risk Scoring: Cost optimization (AlwaysOn vs AutoStop), activity signals, risk score

Output: Rich multi-section panel:

WorkSpaces Investigation Report: ws-0123456789abcdef0
โ”œโ”€ WorkSpace: alice.smith | Bundle: PERFORMANCE (8 vCPU, 32 GB RAM)
โ”œโ”€ Directory: corp-directory | State: AVAILABLE | Last Connection: 2026-04-10 14:22Z
โ”œโ”€
โ”œโ”€ Storage & Performance
โ”‚  โ”œโ”€ Root Volume: 175 GB (SSD, encrypted โœ“)
โ”‚  โ”œโ”€ User Volume: 100 GB (SSD, encrypted โœ“)
โ”‚  โ”œโ”€ Running Mode: AlwaysOn
โ”‚  โ””โ”€ Bundle Type: PERFORMANCE ($25/month)
โ”œโ”€
โ”œโ”€ User & Access
โ”‚  โ”œโ”€ Status: ACTIVE
โ”‚  โ”œโ”€ Active Directory: corp-directory (synced)
โ”‚  โ”œโ”€ MFA Enabled: โœ“ Yes
โ”‚  โ””โ”€ Last 7-Day Access: 5 days active (2 days idle)
โ”œโ”€
โ”œโ”€ Security & Compliance
โ”‚  โ”œโ”€ Encryption at Rest: โœ“ Enabled (KMS, default key)
โ”‚  โ”œโ”€ Tagging: โœ“ 4 tags (cost-center, owner, project, env)
โ”‚  โ”œโ”€ Security Groups: 1 rule (RDP/PCoIP ingress, restricted)
โ”‚  โ””โ”€ Network Interface: eni-abc123 (VPC vpc-def456, subnet subnet-ghi789)
โ”œโ”€
โ”œโ”€ Activity & Usage
โ”‚  โ”œโ”€ Connection History (last 30 days): 18 sessions
โ”‚  โ”œโ”€ Avg Session Duration: 4.5 hours
โ”‚  โ”œโ”€ Estimated Monthly Cost: $25 (AlwaysOn) + storage
โ”‚  โ””โ”€ Optimization Candidate: Consider AutoStop mode ($10/month + $0.33/hour)
โ”œโ”€
โ””โ”€ RISK SCORE: 28/100 [LOW-MODERATE]
   1. OPPORTUNITY: Migrate to AutoStop mode โ€” save $180/year ($25 ร— 12 - 8 hrs/day usage)
   2. Review: User only connects 18 days/month โ€” confirm business requirement
   3. Monitor: Session duration trending for licensing optimization

inventory vpc-investigateยถ

Purpose: 6-phase VPC investigation orchestrator. Audits VPC topology, resource inventory, security posture, network design, compliance, and risk scoring. Identifies unused resources, security gaps, and cost optimization opportunities.

Usage:

runbooks inventory vpc-investigate --vpc-id vpc-0123456789abcdef0 --profile ops
runbooks inventory vpc-investigate --vpc-id vpc-0123456789abcdef0 --profile ops --output json

Options: - --vpc-id (required): VPC ID (e.g., vpc-0123456789abcdef0) - --profile (optional): AWS profile for authentication - --output (optional): json for structured JSON output

Phases: 1. Discovery: VPC CIDR, region, DNS hostnames, DNS resolution, creation date 2. Topology: Subnets (count, CIDR, AZ distribution), route tables, internet gateways, NAT gateways 3. Security: Network ACLs, security groups (count, unused rules), VPC endpoints 4. Network: Transit Gateway attachments, VPC peering, multi-account connectivity, DNS query logging 5. Compliance: VPC Flow Logs (enabled/disabled, retention), CloudTrail logging, encryption 6. Risk Scoring: Resource efficiency, orphaned resources, security gaps, cost optimization score

Output: Rich multi-section panel:

VPC Investigation Report: vpc-0123456789abcdef0
โ”œโ”€ VPC: vpc-0123456789abcdef0 | Region: ap-southeast-2 | CIDR: 10.0.0.0/16
โ”œโ”€ DNS: โœ“ Hostnames enabled | โœ“ Resolution enabled
โ”œโ”€
โ”œโ”€ Topology & Connectivity
โ”‚  โ”œโ”€ Subnets: 6 (2 public, 4 private across 3 AZs)
โ”‚  โ”‚  โ”œโ”€ Public:  10.0.1.0/24 (us-east-2a, 254 IPs available)
โ”‚  โ”‚  โ”œโ”€ Public:  10.0.2.0/24 (us-east-2b, 241 IPs available)
โ”‚  โ”‚  โ”œโ”€ Private: 10.0.11.0/24 (us-east-2a, 128 IPs available)
โ”‚  โ”‚  โ”œโ”€ Private: 10.0.12.0/24 (us-east-2b, 108 IPs available)
โ”‚  โ”‚  โ”œโ”€ Private: 10.0.13.0/24 (us-east-2c, 256 IPs available)
โ”‚  โ”‚  โ””โ”€ Private: 10.0.14.0/24 (us-east-2c, 197 IPs available)
โ”‚  โ”œโ”€
โ”‚  โ”œโ”€ Gateways & NAT
โ”‚  โ”‚  โ”œโ”€ Internet Gateways: 1 (igw-abc123, attached)
โ”‚  โ”‚  โ”œโ”€ NAT Gateways: 3 (1 per AZ, EIP allocated, ~$130/month)
โ”‚  โ”‚  โ””โ”€ Virtual Private Gateway: vpgw-def456 (VPN to on-prem)
โ”‚  โ”œโ”€
โ”‚  โ”œโ”€ Advanced Connectivity
โ”‚  โ”‚  โ”œโ”€ Transit Gateway: Attached (tgw-ghi789)
โ”‚  โ”‚  โ”œโ”€ VPC Peering: 2 connections (dev-vpc, staging-vpc)
โ”‚  โ”‚  โ””โ”€ VPC Endpoints: 3 (S3, DynamoDB, Secrets Manager)
โ”œโ”€
โ”œโ”€ Security Posture
โ”‚  โ”œโ”€ Network ACLs: 6 (all subnets configured)
โ”‚  โ”œโ”€ Security Groups: 12 total
โ”‚  โ”‚  โ”œโ”€ ALB-sg: 1 rule (HTTP/HTTPS ingress, 0.0.0.0/0)
โ”‚  โ”‚  โ”œโ”€ App-sg: 3 rules (1 unused โ€” port 3000 no source flows)
โ”‚  โ”‚  โ”œโ”€ DB-sg: 2 rules (PostgreSQL 5432, restricted to app-sg)
โ”‚  โ”‚  โ””โ”€ Others: 8 groups (review needed)
โ”‚  โ””โ”€ VPC Flow Logs: โœ“ Enabled (CloudWatch Logs, 7-day retention)
โ”œโ”€
โ”œโ”€ Compliance & Monitoring
โ”‚  โ”œโ”€ Flow Logs: โœ“ Enabled | Retention: 7 days | Destination: /aws/vpc/flowlogs/vpc-0123
โ”‚  โ”œโ”€ CloudTrail: โœ“ Data events enabled for VPC API calls
โ”‚  โ”œโ”€ VPC Endpoints: โœ“ Configured (S3, DynamoDB, Secrets Manager)
โ”‚  โ””โ”€ Route Table Logging: โš  No custom logging configured
โ”œโ”€
โ”œโ”€ Resource Inventory
โ”‚  โ”œโ”€ EC2 Instances: 8 running (across 3 subnets)
โ”‚  โ”œโ”€ RDS Instances: 2 (multi-AZ, in private subnets)
โ”‚  โ”œโ”€ ELBs/ALBs: 3 (public-facing, traffic distributed)
โ”‚  โ”œโ”€ Network Interfaces: 22 (18 attached, 4 unattached โš ๏ธ)
โ”‚  โ””โ”€ Elastic IPs: 4 (3 in-use, 1 unassociated โš ๏ธ)
โ”œโ”€
โ””โ”€ RISK SCORE: 34/100 [MODERATE]
   1. CRITICAL: 4 unattached ENIs (cleanup โ†’ save $0/month but reduce clutter)
   2. HIGH: 1 unused security group rule (app-sg:3000) โ€” remove
   3. MEDIUM: 1 unassociated EIP (delete โ†’ save $3.50/month)
   4. OPTIMIZATION: NAT Gateway cost ($130/month) โ€” consider NAT instance for non-prod
   5. MONITORING: Enable VPC endpoint usage logging for cost allocation