runbooks vpc analyze-endpoint-activity

Auto-generated from runbooks vpc analyze-endpoint-activity --help on 2026-05-21. Source of truth: runbooks PyPI package v1.3.22

Usage: runbooks vpc analyze-endpoint-activity [OPTIONS]

  Analyze VPC endpoint activity via CloudTrail (90-day lookback).

  Identifies inactive VPC endpoints (no API calls in lookback period) for
  decommissioning decisions. Supports JIRA FIN-66: 65 endpoints, $18K annual
  savings potential.

  Signals:     - V1: No CloudTrail API calls (90 days) - 45 points
  (decommission candidate)     - Activity count: Number of API calls in
  lookback period     - Last activity date: Most recent CloudTrail event

  Examples:     # Basic analysis (ap-southeast-2, 90-day lookback)
  runbooks vpc analyze-endpoint-activity --profile CENTRALISED_OPS_PROFILE

      # Multi-region with custom lookback     runbooks vpc analyze-endpoint-
      activity \         --profile CENTRALISED_OPS_PROFILE \
      --management-profile MANAGEMENT_PROFILE \         --regions ap-
      southeast-2 --regions ap-southeast-6 \         --lookback-days 60

      # CSV export to custom location     runbooks vpc analyze-endpoint-
      activity \         --profile CENTRALISED_OPS_PROFILE \         --output-
      format csv \         --output-file /tmp/vpce-activity.csv

Options:
  --profile TEXT                  AWS profile for VPC endpoint discovery
                                  [required]
  --regions TEXT                  AWS regions to scan
  --lookback-days INTEGER         CloudTrail lookback period (max: 90 days)
  --output-format [csv|xlsx|json]
                                  Export format
  --output-file PATH              Output file path
  --output-dir PATH               Output directory for exported files
  --help                          Show this message and exit.

Examples