# AWS Cost Calculator (cc)
A CLI tool to quickly calculate AWS costs across multiple accounts.
## Installation
```bash
pip install aws-cost-calculator-cli
```
Or upgrade to the latest version:
```bash
pip install --upgrade aws-cost-calculator-cli
```
## Quick Start
### Authentication Methods
The CLI supports three authentication methods:
#### 1. SSO (Recommended)
```bash
# The CLI will automatically trigger SSO login if needed
cc calculate --profile myprofile --sso my_sso_profile
```
#### 2. Static Credentials
```bash
cc calculate --profile myprofile \
--access-key-id ASIA... \
--secret-access-key ... \
--session-token ...
```
#### 3. Environment Variables
```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
```
### Basic Usage
```bash
# Default: Today minus 2 days, going back 30 days
cc calculate --profile myprofile --sso my_sso_profile
# Specific start date
cc calculate --profile myprofile --sso my_sso_profile --start-date 2025-11-04
# Custom offset and window
cc calculate --profile myprofile --sso my_sso_profile --offset 2 --window 30
# JSON output
cc calculate --profile myprofile --sso my_sso_profile --json-output
```
### 4. Analyze cost trends
All commands support the same authentication options:
```bash
# 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 --sso my_sso_profile --weeks 5
# Custom output file
cc trends --profile myprofile --sso my_sso_profile --output weekly_trends.md
# JSON output
cc trends --profile myprofile --sso my_sso_profile --json-output
```
### 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
- **Start Date**: Defaults to today, or specify with `--start-date`
- **Offset**: Days to go back from start date (default: 2)
- **Window**: Number of days to analyze (default: 30)
Example: If today is Nov 4, 2025:
- With offset=2, window=30: Analyzes Oct 3 - Nov 2 (30 days)
### Cost Calculation
1. **Operational Costs**: Sum of daily costs ÷ window days
2. **Support Allocation**:
- Gets support cost from the analysis month
- Divides by 2 (50% allocation)
- Divides by days in that month
3. **Daily Rate**: Operational + Support per day
4. **Annual Projection**: Daily rate × 365
### Filters Applied
- **Billing Entity**: AWS only (excludes marketplace)
- **Excluded**: Tax, Support (calculated separately)
- **Metric**: Net Amortized Cost
## Configuration
Profiles are stored in: `~/.config/cost-calculator/profiles.json`
Example:
```json
{
"myprofile": {
"aws_profile": "my_aws_profile",
"accounts": ["123456789012", "234567890123", "345678901234"]
}
}
```
## Examples
```bash
# Quick daily check
cc calculate --profile myprofile
# Historical analysis
cc calculate --profile myprofile --start-date 2025-10-01
# Export to JSON for processing
cc calculate --profile myprofile --json-output > costs.json
# Different window size
cc calculate --profile myprofile --window 60
# Weekly cost trends analysis
cc trends --profile myprofile
# Analyze last 8 weeks
cc trends --profile myprofile --weeks 8
# Monthly cost trends analysis
cc monthly --profile myprofile
# Analyze last 12 months
cc monthly --profile myprofile --months 12
# Drill down into specific service
cc drill --profile myprofile --service "EC2 - Other"
# Drill down into specific account
cc drill --profile myprofile --account 123456789012
# Drill down into service within account
cc drill --profile myprofile --service "EC2 - Other" --account 123456789012
```
## Trends Report
The `trends` command generates a markdown report with **two types of analysis**:
### 1. Week-over-Week (WoW)
Compares each week to the previous week - good for catching immediate spikes and changes.
### 2. Trailing 30-Day (T-30)
Compares each week to the same week 4 weeks ago - filters out noise and shows sustained trends.
**Features:**
- **Service-level aggregation**: Shows total cost per service (not individual usage types)
- **Top 10 Increases/Decreases**: For each comparison period
- **Total rows**: Sum of top 10 changes for quick assessment
- **Filters**: Only shows changes >$10 and >5%
Example output:
```
Week of Oct 19 → Week of Oct 26 (WoW)
Increases: 4, Decreases: 10
Top: EC2 - Other (+$949.12)
Week of Oct 26 vs Week of Sep 28 (T-30)
Increases: 10, Decreases: 10
Top: EC2 - Other (+$886.39)
```
The report is saved to `cost_trends.md` by default and includes:
- Service name
- Previous/baseline cost
- Current cost
- Change amount and percentage
- Total of top 10 changes
## Monthly Report
The `monthly` command generates month-over-month cost comparisons:
**Features:**
- **Service-level aggregation**: Shows total cost per service
- **Calendar month comparisons**: October vs September, September vs August, etc.
- **Top 10 Increases/Decreases**: For each month comparison
- **Total rows**: Sum of top 10 changes
- **Filters**: Only shows changes >$50 and >5%
Example output:
```
October 2025 → November 2025
Increases: 1, Decreases: 10
Top: Savings Plans for AWS Compute usage (+$231,161.46)
```
The report is saved to `monthly_trends.md` by default.
## Drill-Down Analysis
The `drill` command allows you to investigate cost changes at different levels of detail:
**Funnel Approach:**
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
- **Search & filter**: Find services by pattern or cost threshold
- **Profile management**: CRUD operations for account profiles in DynamoDB
- **Markdown reports**: Generate formatted reports
- **JSON output**: Machine-readable output for automation
- **Lambda API backend**: Serverless backend with pandas/numpy support
Example output:
```
# Drill by service
cc drill --profile myprofile --service "EC2 - Other"
Showing top accounts:
Week of Oct 19 → Week of Oct 26
Increases: 3, Decreases: 2
Top: 123456789012 (+$450.23)
```
The report is saved to `drill_down.md` by default.
## Output
```
Analyzing: 2025-10-03 to 2025-11-02 (30 days)
AWS Profile: my_aws_profile
Accounts: 3
Fetching cost data...
Fetching support costs...
============================================================
Period: 2025-10-03 to 2025-11-02
Days analyzed: 30
============================================================
Total operational cost: $450,000.00
Daily operational: $14,516.13
Support (month): $15,000.00
Support per day (÷2÷days): $241.94
============================================================
DAILY RATE: $14,758.07
ANNUAL PROJECTION: $5,386,695
============================================================
```
Raw data
{
"_id": null,
"home_page": "https://github.com/trilogy-group/aws-cost-calculator",
"name": "aws-cost-calculator-cli",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "aws cost calculator billing optimization cloud",
"author": "Cost Optimization Team",
"author_email": null,
"download_url": "https://files.pythonhosted.org/packages/39/82/01c490692d982b63ebf8c8c52648f81dfc03962d9b76fadb1c14452aeb98/aws_cost_calculator_cli-2.0.1.tar.gz",
"platform": null,
"description": "# AWS Cost Calculator (cc)\n\nA CLI tool to quickly calculate AWS costs across multiple accounts.\n\n## Installation\n\n```bash\npip install aws-cost-calculator-cli\n```\n\nOr upgrade to the latest version:\n```bash\npip install --upgrade aws-cost-calculator-cli\n```\n\n## Quick Start\n\n### Authentication Methods\n\nThe CLI supports three authentication methods:\n\n#### 1. SSO (Recommended)\n```bash\n# The CLI will automatically trigger SSO login if needed\ncc calculate --profile myprofile --sso my_sso_profile\n```\n\n#### 2. Static Credentials\n```bash\ncc calculate --profile myprofile \\\n --access-key-id ASIA... \\\n --secret-access-key ... \\\n --session-token ...\n```\n\n#### 3. Environment Variables\n```bash\n# For SSO\nexport AWS_PROFILE=my_sso_profile\ncc calculate --profile myprofile\n\n# For static credentials\nexport AWS_ACCESS_KEY_ID=ASIA...\nexport AWS_SECRET_ACCESS_KEY=...\nexport AWS_SESSION_TOKEN=...\ncc calculate --profile myprofile\n```\n\n### Basic Usage\n\n```bash\n# Default: Today minus 2 days, going back 30 days\ncc calculate --profile myprofile --sso my_sso_profile\n\n# Specific start date\ncc calculate --profile myprofile --sso my_sso_profile --start-date 2025-11-04\n\n# Custom offset and window\ncc calculate --profile myprofile --sso my_sso_profile --offset 2 --window 30\n\n# JSON output\ncc calculate --profile myprofile --sso my_sso_profile --json-output\n```\n\n### 4. Analyze cost trends\n\nAll commands support the same authentication options:\n\n```bash\n# With SSO\ncc trends --profile myprofile --sso my_sso_profile\n\n# With static credentials\ncc trends --profile myprofile --access-key-id ASIA... --secret-access-key ... --session-token ...\n\n# With environment variables\nexport AWS_PROFILE=my_sso_profile\ncc trends --profile myprofile\n\n# Analyze more weeks\ncc trends --profile myprofile --sso my_sso_profile --weeks 5\n\n# Custom output file\ncc trends --profile myprofile --sso my_sso_profile --output weekly_trends.md\n\n# JSON output\ncc trends --profile myprofile --sso my_sso_profile --json-output\n```\n\n### 5. Monthly and drill-down analysis\n\n```bash\n# Monthly trends\ncc monthly --profile myprofile --sso my_sso_profile\n\n# Drill down by service\ncc drill --profile myprofile --sso my_sso_profile --service \"EC2 - Other\"\n\n# Drill down by account\ncc drill --profile myprofile --sso my_sso_profile --account 123456789012\n```\n\n### 6. List profiles\n\n```bash\ncc list-profiles\n```\n\n## Authentication\n\n### Overview\n\nThe CLI supports three authentication methods, all of which work with every command (`calculate`, `trends`, `monthly`, `drill`):\n\n### Method 1: SSO (Recommended)\n\nThe CLI automatically handles SSO login if your session has expired:\n\n```bash\ncc calculate --profile myprofile --sso my_sso_profile\n```\n\n**How it works:**\n1. CLI checks if SSO session is valid using `aws sts get-caller-identity`\n2. If expired, automatically runs `aws sso login --profile my_sso_profile`\n3. Opens browser for authentication\n4. Proceeds with cost calculation once authenticated\n\n**Benefits:**\n- No manual SSO login required\n- Automatic session refresh\n- Most secure method\n- Works with AWS IAM Identity Center\n\n### Method 2: Static Credentials\n\nPass temporary credentials directly via CLI flags:\n\n```bash\ncc calculate --profile myprofile \\\n --access-key-id ASIA... \\\n --secret-access-key ... \\\n --session-token ...\n```\n\n**Use cases:**\n- CI/CD pipelines\n- Temporary credentials from STS\n- Automated scripts\n- When SSO is not available\n\n### Method 3: Environment Variables\n\nSet credentials in your shell environment:\n\n```bash\n# For SSO\nexport AWS_PROFILE=my_sso_profile\ncc calculate --profile myprofile\n\n# For static credentials\nexport AWS_ACCESS_KEY_ID=ASIA...\nexport AWS_SECRET_ACCESS_KEY=...\nexport AWS_SESSION_TOKEN=...\ncc calculate --profile myprofile\n```\n\n**Benefits:**\n- No need to pass credentials with each command\n- Works with existing AWS CLI configuration\n- Can be set in shell profile (~/.zshrc, ~/.bashrc)\n\n### Profile Configuration\n\nProfiles can be stored locally or fetched from a backend API:\n\n**Local storage:** `~/.config/cost-calculator/profiles.json`\n```json\n{\n \"myprofile\": {\n \"accounts\": [\"123456789012\", \"234567890123\", ...]\n }\n}\n```\n\n**Backend API:** Set `COST_API_SECRET` environment variable\n\nQuick setup (saves to shell profile):\n```bash\ncc setup-api\n# Enter your API secret when prompted (input will be hidden)\n```\n\n**CUR Configuration (for --resources flag):**\n\nTo use resource-level queries, configure CUR settings:\n```bash\ncc setup-cur\n# Enter: Database name, table name, S3 output location\n```\n\nThis saves configuration to `~/.config/cost-calculator/cur_config.json`\n\nOr set manually:\n```bash\nexport COST_API_SECRET=\"your-api-secret\"\ncc calculate --profile myprofile --sso my_sso_profile\n```\n\nThe CLI will automatically fetch profile configuration from the backend if `COST_API_SECRET` is set.\n\n## How It Works\n\n### Date Calculation\n- **Start Date**: Defaults to today, or specify with `--start-date`\n- **Offset**: Days to go back from start date (default: 2)\n- **Window**: Number of days to analyze (default: 30)\n\nExample: If today is Nov 4, 2025:\n- With offset=2, window=30: Analyzes Oct 3 - Nov 2 (30 days)\n\n### Cost Calculation\n1. **Operational Costs**: Sum of daily costs \u00f7 window days\n2. **Support Allocation**: \n - Gets support cost from the analysis month\n - Divides by 2 (50% allocation)\n - Divides by days in that month\n3. **Daily Rate**: Operational + Support per day\n4. **Annual Projection**: Daily rate \u00d7 365\n\n### Filters Applied\n- **Billing Entity**: AWS only (excludes marketplace)\n- **Excluded**: Tax, Support (calculated separately)\n- **Metric**: Net Amortized Cost\n\n## Configuration\n\nProfiles are stored in: `~/.config/cost-calculator/profiles.json`\n\nExample:\n```json\n{\n \"myprofile\": {\n \"aws_profile\": \"my_aws_profile\",\n \"accounts\": [\"123456789012\", \"234567890123\", \"345678901234\"]\n }\n}\n```\n\n## Examples\n\n```bash\n# Quick daily check\ncc calculate --profile myprofile\n\n# Historical analysis\ncc calculate --profile myprofile --start-date 2025-10-01\n\n# Export to JSON for processing\ncc calculate --profile myprofile --json-output > costs.json\n\n# Different window size\ncc calculate --profile myprofile --window 60\n\n# Weekly cost trends analysis\ncc trends --profile myprofile\n\n# Analyze last 8 weeks\ncc trends --profile myprofile --weeks 8\n\n# Monthly cost trends analysis\ncc monthly --profile myprofile\n\n# Analyze last 12 months\ncc monthly --profile myprofile --months 12\n\n# Drill down into specific service\ncc drill --profile myprofile --service \"EC2 - Other\"\n\n# Drill down into specific account\ncc drill --profile myprofile --account 123456789012\n\n# Drill down into service within account\ncc drill --profile myprofile --service \"EC2 - Other\" --account 123456789012\n```\n\n## Trends Report\n\nThe `trends` command generates a markdown report with **two types of analysis**:\n\n### 1. Week-over-Week (WoW)\nCompares each week to the previous week - good for catching immediate spikes and changes.\n\n### 2. Trailing 30-Day (T-30)\nCompares each week to the same week 4 weeks ago - filters out noise and shows sustained trends.\n\n**Features:**\n- **Service-level aggregation**: Shows total cost per service (not individual usage types)\n- **Top 10 Increases/Decreases**: For each comparison period\n- **Total rows**: Sum of top 10 changes for quick assessment\n- **Filters**: Only shows changes >$10 and >5%\n\nExample output:\n```\nWeek of Oct 19 \u2192 Week of Oct 26 (WoW)\n Increases: 4, Decreases: 10\n Top: EC2 - Other (+$949.12)\n\nWeek of Oct 26 vs Week of Sep 28 (T-30)\n Increases: 10, Decreases: 10\n Top: EC2 - Other (+$886.39)\n```\n\nThe report is saved to `cost_trends.md` by default and includes:\n- Service name\n- Previous/baseline cost\n- Current cost\n- Change amount and percentage\n- Total of top 10 changes\n\n## Monthly Report\n\nThe `monthly` command generates month-over-month cost comparisons:\n\n**Features:**\n- **Service-level aggregation**: Shows total cost per service\n- **Calendar month comparisons**: October vs September, September vs August, etc.\n- **Top 10 Increases/Decreases**: For each month comparison\n- **Total rows**: Sum of top 10 changes\n- **Filters**: Only shows changes >$50 and >5%\n\nExample output:\n```\nOctober 2025 \u2192 November 2025\n Increases: 1, Decreases: 10\n Top: Savings Plans for AWS Compute usage (+$231,161.46)\n```\n\nThe report is saved to `monthly_trends.md` by default.\n\n## Drill-Down Analysis\n\nThe `drill` command allows you to investigate cost changes at different levels of detail:\n\n**Funnel Approach:**\n1. **Start broad:** `cc trends` \u2192 See EC2 costs up $1000\n2. **Drill by service:** `cc drill --service \"EC2 - Other\"` \u2192 See which accounts\n3. **Drill deeper:** `cc drill --service \"EC2 - Other\" --account 123` \u2192 See usage types\n4. **Resource-level:** `cc drill --service \"EC2 - Other\" --account 123 --resources` \u2192 See individual instance IDs\n\n**Features:**\n- **Week-over-week cost analysis**: Compare costs between consecutive weeks\n- **Month-over-month cost analysis**: Compare costs between consecutive months\n- **Drill-down analysis**: Analyze costs by service, account, or usage type\n- **Resource-level analysis**: See individual resource IDs and costs using CUR data (NEW in v1.7.0)\n- **Pandas aggregations**: Time series analysis with sum, avg, std across all weeks\n- **Volatility detection**: Identify services with high cost variability and outliers\n- **Trend detection**: Auto-detect increasing/decreasing cost patterns\n- **Search & filter**: Find services by pattern or cost threshold\n- **Profile management**: CRUD operations for account profiles in DynamoDB\n- **Markdown reports**: Generate formatted reports\n- **JSON output**: Machine-readable output for automation\n- **Lambda API backend**: Serverless backend with pandas/numpy support\n\nExample output:\n```\n# Drill by service\ncc drill --profile myprofile --service \"EC2 - Other\"\n\nShowing top accounts:\nWeek of Oct 19 \u2192 Week of Oct 26\n Increases: 3, Decreases: 2\n Top: 123456789012 (+$450.23)\n```\n\nThe report is saved to `drill_down.md` by default.\n\n## Output\n\n```\nAnalyzing: 2025-10-03 to 2025-11-02 (30 days)\nAWS Profile: my_aws_profile\nAccounts: 3\n\nFetching cost data...\nFetching support costs...\n============================================================\nPeriod: 2025-10-03 to 2025-11-02\nDays analyzed: 30\n============================================================\nTotal operational cost: $450,000.00\nDaily operational: $14,516.13\nSupport (month): $15,000.00\nSupport per day (\u00f72\u00f7days): $241.94\n============================================================\nDAILY RATE: $14,758.07\nANNUAL PROJECTION: $5,386,695\n============================================================\n```\n",
"bugtrack_url": null,
"license": null,
"summary": "AWS Cost Calculator CLI - Calculate daily and annual AWS costs across multiple accounts",
"version": "2.0.1",
"project_urls": {
"Documentation": "https://github.com/trilogy-group/aws-cost-calculator/blob/main/README.md",
"Homepage": "https://github.com/trilogy-group/aws-cost-calculator"
},
"split_keywords": [
"aws",
"cost",
"calculator",
"billing",
"optimization",
"cloud"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "5b15dc925c9e2d43a73e345e74fad1c08337ab5d08933e2b66580314e9c2cc29",
"md5": "98c077b46bb9550a783cbde1edb02aa5",
"sha256": "6ab00be49c1d61206f86212197980f6567d72ae18799b79a7d3ccc0fad298579"
},
"downloads": -1,
"filename": "aws_cost_calculator_cli-2.0.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "98c077b46bb9550a783cbde1edb02aa5",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 41241,
"upload_time": "2025-11-09T07:49:55",
"upload_time_iso_8601": "2025-11-09T07:49:55.623759Z",
"url": "https://files.pythonhosted.org/packages/5b/15/dc925c9e2d43a73e345e74fad1c08337ab5d08933e2b66580314e9c2cc29/aws_cost_calculator_cli-2.0.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "398201c490692d982b63ebf8c8c52648f81dfc03962d9b76fadb1c14452aeb98",
"md5": "f4f5167855d7687e7f2e80db88117b9e",
"sha256": "809f76814067ed78408802f9c7d54ee29b0455307bc2889b471c849b9be50330"
},
"downloads": -1,
"filename": "aws_cost_calculator_cli-2.0.1.tar.gz",
"has_sig": false,
"md5_digest": "f4f5167855d7687e7f2e80db88117b9e",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 40215,
"upload_time": "2025-11-09T07:49:57",
"upload_time_iso_8601": "2025-11-09T07:49:57.007095Z",
"url": "https://files.pythonhosted.org/packages/39/82/01c490692d982b63ebf8c8c52648f81dfc03962d9b76fadb1c14452aeb98/aws_cost_calculator_cli-2.0.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-11-09 07:49:57",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "trilogy-group",
"github_project": "aws-cost-calculator",
"github_not_found": true,
"lcname": "aws-cost-calculator-cli"
}
JSON
