aws-cost-calculator-cli 1.6.0__py3-none-any.whl → 1.9.1__py3-none-any.whl

{aws_cost_calculator_cli-1.6.0.dist-info → aws_cost_calculator_cli-1.9.1.dist-info}/METADATA

@@ -1,11 +1,11 @@
 Metadata-Version: 2.4
 Name: aws-cost-calculator-cli
-Version: 1.6.0
+Version: 1.9.1
 Summary: AWS Cost Calculator CLI - Calculate daily and annual AWS costs across multiple accounts
-Home-page: https://github.com/yourusername/cost-calculator
+Home-page: https://github.com/trilogy-group/aws-cost-calculator
 Author: Cost Optimization Team
 Author-email: 
-Project-URL: Documentation, https://github.com/yourusername/cost-calculator/blob/main/README.md
+Project-URL: Documentation, https://github.com/trilogy-group/aws-cost-calculator/blob/main/README.md
 Keywords: aws cost calculator billing optimization cloud
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
@@ -43,8 +43,12 @@ A CLI tool to quickly calculate AWS costs across multiple accounts.
 ## Installation
 
 ```bash
-cd ~/cost-calculator
-pip install -e .
+pip install aws-cost-calculator-cli
+```
+
+Or upgrade to the latest version:
+```bash
+pip install --upgrade aws-cost-calculator-cli
 ```
 
 ## Quick Start
@@ -56,68 +60,193 @@ The CLI supports three authentication methods:
 #### 1. SSO (Recommended)
 ```bash
 # The CLI will automatically trigger SSO login if needed
-cc calculate --profile khoros --sso khoros_umbrella
+cc calculate --profile myprofile --sso my_sso_profile
 ```
 
 #### 2. Static Credentials
 ```bash
-cc calculate --profile khoros \
-  --access-key-id ASIA3D3QOXPO6EBAPXVI \
-  --secret-access-key /9ijZEUoszN/S2A8IlCrHpW+1fMZ7aUb7fPvU0dL \
-  --session-token IQoJb3JpZ2luX2VjENr...
+cc calculate --profile myprofile \
+  --access-key-id ASIA... \
+  --secret-access-key ... \
+  --session-token ...
 ```
 
 #### 3. Environment Variables
 ```bash
 # For SSO
-export AWS_PROFILE=khoros_umbrella
-cc calculate --profile khoros
+export AWS_PROFILE=my_sso_profile
+cc calculate --profile myprofile
 
 # For static credentials
 export AWS_ACCESS_KEY_ID=ASIA...
 export AWS_SECRET_ACCESS_KEY=...
 export AWS_SESSION_TOKEN=...
-cc calculate --profile khoros
+cc calculate --profile myprofile
 ```
 
 ### Basic Usage
 
 ```bash
 # Default: Today minus 2 days, going back 30 days
-cc calculate --profile khoros --sso khoros_umbrella
+cc calculate --profile myprofile --sso my_sso_profile
 
 # Specific start date
-cc calculate --profile khoros --sso khoros_umbrella --start-date 2025-11-04
+cc calculate --profile myprofile --sso my_sso_profile --start-date 2025-11-04
 
 # Custom offset and window
-cc calculate --profile khoros --sso khoros_umbrella --offset 2 --window 30
+cc calculate --profile myprofile --sso my_sso_profile --offset 2 --window 30
 
 # JSON output
-cc calculate --profile khoros --sso khoros_umbrella --json-output
+cc calculate --profile myprofile --sso my_sso_profile --json-output
 ```
 
 ### 4. Analyze cost trends
 
+All commands support the same authentication options:
+
 ```bash
-# Analyze last 3 weeks (default)
+# With SSO
+cc trends --profile myprofile --sso my_sso_profile
+
+# With static credentials
+cc trends --profile myprofile --access-key-id ASIA... --secret-access-key ... --session-token ...
+
+# With environment variables
+export AWS_PROFILE=my_sso_profile
 cc trends --profile myprofile
 
 # Analyze more weeks
-cc trends --profile myprofile --weeks 5
+cc trends --profile myprofile --sso my_sso_profile --weeks 5
 
 # Custom output file
-cc trends --profile myprofile --output weekly_trends.md
+cc trends --profile myprofile --sso my_sso_profile --output weekly_trends.md
 
 # JSON output
-cc trends --profile myprofile --json-output
+cc trends --profile myprofile --sso my_sso_profile --json-output
 ```
 
-### 5. List profiles
+### 5. Monthly and drill-down analysis
+
+```bash
+# Monthly trends
+cc monthly --profile myprofile --sso my_sso_profile
+
+# Drill down by service
+cc drill --profile myprofile --sso my_sso_profile --service "EC2 - Other"
+
+# Drill down by account
+cc drill --profile myprofile --sso my_sso_profile --account 123456789012
+```
+
+### 6. List profiles
 
 ```bash
 cc list-profiles
 ```
 
+## Authentication
+
+### Overview
+
+The CLI supports three authentication methods, all of which work with every command (`calculate`, `trends`, `monthly`, `drill`):
+
+### Method 1: SSO (Recommended)
+
+The CLI automatically handles SSO login if your session has expired:
+
+```bash
+cc calculate --profile myprofile --sso my_sso_profile
+```
+
+**How it works:**
+1. CLI checks if SSO session is valid using `aws sts get-caller-identity`
+2. If expired, automatically runs `aws sso login --profile my_sso_profile`
+3. Opens browser for authentication
+4. Proceeds with cost calculation once authenticated
+
+**Benefits:**
+- No manual SSO login required
+- Automatic session refresh
+- Most secure method
+- Works with AWS IAM Identity Center
+
+### Method 2: Static Credentials
+
+Pass temporary credentials directly via CLI flags:
+
+```bash
+cc calculate --profile myprofile \
+  --access-key-id ASIA... \
+  --secret-access-key ... \
+  --session-token ...
+```
+
+**Use cases:**
+- CI/CD pipelines
+- Temporary credentials from STS
+- Automated scripts
+- When SSO is not available
+
+### Method 3: Environment Variables
+
+Set credentials in your shell environment:
+
+```bash
+# For SSO
+export AWS_PROFILE=my_sso_profile
+cc calculate --profile myprofile
+
+# For static credentials
+export AWS_ACCESS_KEY_ID=ASIA...
+export AWS_SECRET_ACCESS_KEY=...
+export AWS_SESSION_TOKEN=...
+cc calculate --profile myprofile
+```
+
+**Benefits:**
+- No need to pass credentials with each command
+- Works with existing AWS CLI configuration
+- Can be set in shell profile (~/.zshrc, ~/.bashrc)
+
+### Profile Configuration
+
+Profiles can be stored locally or fetched from a backend API:
+
+**Local storage:** `~/.config/cost-calculator/profiles.json`
+```json
+{
+  "myprofile": {
+    "accounts": ["123456789012", "234567890123", ...]
+  }
+}
+```
+
+**Backend API:** Set `COST_API_SECRET` environment variable
+
+Quick setup (saves to shell profile):
+```bash
+cc setup-api
+# Enter your API secret when prompted (input will be hidden)
+```
+
+**CUR Configuration (for --resources flag):**
+
+To use resource-level queries, configure CUR settings:
+```bash
+cc setup-cur
+# Enter: Database name, table name, S3 output location
+```
+
+This saves configuration to `~/.config/cost-calculator/cur_config.json`
+
+Or set manually:
+```bash
+export COST_API_SECRET="your-api-secret"
+cc calculate --profile myprofile --sso my_sso_profile
+```
+
+The CLI will automatically fetch profile configuration from the backend if `COST_API_SECRET` is set.
+
 ## How It Works
 
 ### Date Calculation
@@ -255,11 +384,13 @@ The `drill` command allows you to investigate cost changes at different levels o
 1. **Start broad:** `cc trends` → See EC2 costs up $1000
 2. **Drill by service:** `cc drill --service "EC2 - Other"` → See which accounts
 3. **Drill deeper:** `cc drill --service "EC2 - Other" --account 123` → See usage types
+4. **Resource-level:** `cc drill --service "EC2 - Other" --account 123 --resources` → See individual instance IDs
 
 **Features:**
 - **Week-over-week cost analysis**: Compare costs between consecutive weeks
 - **Month-over-month cost analysis**: Compare costs between consecutive months
 - **Drill-down analysis**: Analyze costs by service, account, or usage type
+- **Resource-level analysis**: See individual resource IDs and costs using CUR data (NEW in v1.7.0)
 - **Pandas aggregations**: Time series analysis with sum, avg, std across all weeks
 - **Volatility detection**: Identify services with high cost variability and outliers
 - **Trend detection**: Auto-detect increasing/decreasing cost patterns
@@ -277,7 +408,7 @@ cc drill --profile myprofile --service "EC2 - Other"
 Showing top accounts:
 Week of Oct 19 → Week of Oct 26
   Increases: 3, Decreases: 2
-  Top: 887649220066 (+$450.23)
+  Top: 123456789012 (+$450.23)
 ```
 
 The report is saved to `drill_down.md` by default.

aws_cost_calculator_cli-1.9.1.dist-info/RECORD

@@ -0,0 +1,15 @@
+aws_cost_calculator_cli-1.9.1.dist-info/licenses/LICENSE,sha256=cYtmQZHNGGTXOtg3T7LHDRneleaH0dHXHfxFV3WR50Y,1079
+cost_calculator/__init__.py,sha256=PJeIqvWh5AYJVrJxPPkI4pJnAt37rIjasrNS0I87kaM,52
+cost_calculator/api_client.py,sha256=4ZI2XcGIN3FBeQqb7xOxQ91kCoeM43-rExiOELXoKBQ,2485
+cost_calculator/cli.py,sha256=IRlRxefn9rfrt6EWwSEcMi9HCISHuOfnUs2_Bf5IZkA,54085
+cost_calculator/cur.py,sha256=QaZ_nyDSw5_cti-h5Ho6eYLbqzY5TWoub24DpyzIiSs,9502
+cost_calculator/drill.py,sha256=hGi-prLgZDvNMMICQc4fl3LenM7YaZ3To_Ei4LKwrdc,10543
+cost_calculator/executor.py,sha256=vZX3BCgTRHwBfxC0WqQsHgv1ww5rpmKqLCTrW2sflSY,6509
+cost_calculator/forensics.py,sha256=uhRo3I_zOeMEaBENHfgq65URga31W0Z4vzS2UN6VmTY,12819
+cost_calculator/monthly.py,sha256=6k9F8S7djhX1wGV3-T1MZP7CvWbbfhSTEaddwCfVu5M,7932
+cost_calculator/trends.py,sha256=k_s4ylBX50sqoiM_fwepi58HW01zz767FMJhQUPDznk,12246
+aws_cost_calculator_cli-1.9.1.dist-info/METADATA,sha256=jMNKiSSMAbMNajhVxBOyzSuJaWg3lrGfuCBSz0THo38,11978
+aws_cost_calculator_cli-1.9.1.dist-info/WHEEL,sha256=Nw36Djuh_5VDukK0H78QzOX-_FQEo6V37m3nkm96gtU,91
+aws_cost_calculator_cli-1.9.1.dist-info/entry_points.txt,sha256=_5Qy4EcHbYVYrdgOu1E48faMHb9fLUl5VJ3djDHuJBo,47
+aws_cost_calculator_cli-1.9.1.dist-info/top_level.txt,sha256=PRwGPPlNqASfyhGHDjSfyl4SXeE7GF3OVTu1tY1Uqyc,16
+aws_cost_calculator_cli-1.9.1.dist-info/RECORD,,

{aws_cost_calculator_cli-1.6.0.dist-info → aws_cost_calculator_cli-1.9.1.dist-info}/WHEEL

@@ -1,5 +1,5 @@
 Wheel-Version: 1.0
-Generator: setuptools (80.9.0)
+Generator: setuptools (80.7.1)
 Root-Is-Purelib: true
 Tag: py3-none-any
 

cost_calculator/api_client.py

@@ -50,7 +50,8 @@ def call_lambda_api(endpoint, credentials, accounts, **kwargs):
         'monthly': 'https://6aueebodw6q4zdeu3aaexb6tle0fqhhr.lambda-url.us-east-1.on.aws/',
         'drill': 'https://3ncm2gzxrsyptrhud3ua3x5lju0akvsr.lambda-url.us-east-1.on.aws/',
         'analyze': 'https://y6npmidtxwzg62nrqzkbacfs5q0edwgs.lambda-url.us-east-1.on.aws/',
-        'profiles': 'https://64g7jq7sjygec2zmll5lsghrpi0txrzo.lambda-url.us-east-1.on.aws/'
+        'profiles': 'https://64g7jq7sjygec2zmll5lsghrpi0txrzo.lambda-url.us-east-1.on.aws/',
+        'forensics': 'https://gaekfzz7sc2hwn4mjyk64sieke0vadfo.lambda-url.us-east-1.on.aws/'  # Will be populated after deployment
     }
     
     url = endpoint_urls.get(endpoint)