Skip to main content

Quickstart

Get up and running with Cloud Cost Analyzer in under 5 minutes. It is three steps:

  1. Install the CLI (Step 1).
  2. Log in to get a free API key (Step 2.5). No browser on this machine? Run cca login --device, or set CCA_API_KEY to a key from the API Keys page.
  3. Run it: cca demo for a sample report, then cca scan on your own account (Step 3).

Prerequisites​

  • AWS or Azure credentials configured locally
  • macOS (arm64), Linux (x86_64 / arm64), or Windows (x86_64) - all have native binaries

Step 1: Install the CLI​

curl -sSL https://releases.dragonfractal.com/install.sh | sh

Verify the installation:

cca --version

Step 1.5: See a sample report (optional)​

Before wiring up credentials or a key, run the built-in demo to see exactly what a report looks like. It uses sample data: no account, no cloud credentials, no network.

cca demo

Add --all to see every finding, or --output json to see the machine-readable shape.

Step 2: Grant Read-Only Access​

cca setup provisions the read-only permissions a scan needs. Preview exactly what it will grant with --output-template (nothing is changed), then apply it with --deploy.

Corporate or restricted environment?

--deploy creates IAM roles / service principals, which needs cloud-admin rights you may not have. If so, run cca setup --provider <aws|azure> --output-template to get the exact read-only policy and hand it to whoever provisions access. The provider guides cover the rights each path needs and the common enterprise gotchas (AWS SSO, Entra security defaults): AWS and Azure.

# See the exact IAM policy CCA will create (read-only; nothing is changed yet)
cca setup --provider aws --output-template

# Create the read-only IAM role via CloudFormation (needs the AWS CLI configured)
cca setup --provider aws --deploy

--deploy creates a CloudCostAnalyzerRole with read-only access and prints its ARN. Prefer to bring your own credentials? CCA uses the standard AWS credential chain:

export AWS_ACCESS_KEY_ID=your-key
export AWS_SECRET_ACCESS_KEY=your-secret
export AWS_REGION=us-east-1
# or run: aws configure
# or attach an EC2/ECS/Lambda IAM role (auto-detected)
note

GCP scanning is on the roadmap and not supported yet, so there is no GCP setup step.

Step 2.5: Sign In​

Sign in once and the CLI stores a free API key locally, so later scans need no key flags:

cca login

This opens your browser to sign in with Google, GitHub, or email. cca login detects an SSH session or a Linux machine with no display, and switches to the device-code flow on its own. In CI, set CCA_API_KEY instead (see below). You can also ask for it directly:

cca login --device

The device-code flow prints a link and a short code. Open the link on any device that has a browser (your laptop or phone), sign in, and enter the code. The terminal finishes signing in by itself. If the machine you are on does have a browser but looks headless (for example a desktop you reached over SSH), force the browser flow with cca login --browser.

No browser anywhere near the machine? Create an API key on the API Keys page from any device, then either run CCA_API_KEY=<key> cca login once (this keeps the key out of your shell history and process list) or export CCA_API_KEY=<key>. No sign-in step is needed after that.

New accounts can scan right away on a free preview (a few scans in the first week); verifying your email removes the limit. Signing in with Google or GitHub is already verified, so there is no limit.

For CI, you can skip cca login and pass a key directly with --api-key or the CCA_API_KEY environment variable (create one on the API Keys page).

Step 3: Run Your First Scan​

# Uses the key stored by `cca login` plus your AWS credentials
cca scan -r us-east-1

# A specific AWS region
cca scan -r us-west-2

# CI / explicit key (no `cca login` needed)
cca scan --api-key $CCA_API_KEY -r us-east-1

# Or with Docker (pass the key via the environment)
docker run --rm \
-e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e CCA_API_KEY \
dragonfractal/cca:latest \
scan -r us-east-1

Example output. The report opens with an executive summary — total spend, potential savings, and the top opportunities by service:

cca scan executive summary showing $2,986/mo in potential savings across 364 resources

...followed by the detailed findings, each with the evidence behind it and a remediation step:

cca scan detailed findings, each with evidence and a remediation step

note

Resource IDs are redacted in these example images.

Step 4: Export Results​

# Save as JSON
cca scan --provider aws --output json --output-file results.json

# Save as a Markdown report
cca scan --provider aws --output markdown --output-file report.md

# Generate a PDF report (Pro and Enterprise only, see the note below)
cca scan --provider aws --output pdf --output-file report.pdf
PDF and CSV export need a paid plan

table, json, yaml and markdown are free. On the Free plan, --output pdf and --output csv run the scan and then stop with 'pdf' export is a paid feature, because the CLI learns your plan from the service only after the scan. Nothing is lost: the scan is saved to your account, and re-running with --output json or --output markdown gives you the same data. Upgrade to Professional to export PDF and CSV.

Step 5: Sync with Dashboard (Optional)​

For team collaboration and tracking optimization progress over time, sync your scans to the cloud dashboard.

Create an API Key​

  1. Sign up at cca.dragonfractal.com
  2. Go to the API Keys page
  3. Click Create API Key
  4. Copy the key

Run Managed Scan​

# Set your API key
export CCA_API_KEY=cca_live_xxxxx

# Run scan in managed mode
cca scan --provider aws --mode managed

# Or pass the key directly
cca scan --provider aws --mode managed --api-key cca_live_xxxxx

View your scan results in the Dashboard — savings, optimization score, and findings tracked over time across your team:

Cloud Cost Analyzer dashboard showing monthly savings, optimization score, and recent scans

Next Steps​