Skip to main content

AWS Fleet Scout

Scout optimal AWS compute for cluster workloads. Compare spot, capacity blocks, and on-demand pricing across regions and instance types. Auto-discover instances for CPU and GPU deployments with HPC schedulers.

Features

  • Compare: Side-by-side comparison of Spot, Capacity Blocks, and On-Demand pricing
  • Auto-Discovery: Automatically find all instances matching a prefix (e.g., all P-series, G-series)
  • Quota Validation: Automatic checking against AWS Service Quotas with actionable warnings
  • Smart Caching: Reference data cached locally to minimize API calls and improve performance
  • Capacity Calendar: Flight-booking style calendar view of capacity block availability
  • Fleet Packing: Find optimal regions for mixed instance type deployments
  • Placement Engine: Ranked recommendations with customizable constraints
  • Composite Utility: Combine spot stability, pricing, and latency scores
  • Spot Scores: Query placement scores and pricing for spot instances
  • Read-Only: Safe to use - only queries AWS APIs, never creates/modifies resources

Installation

Per PyPI:

pip install aws-fleet-scout

From source:

git clone https://github.com/markodjukic/aws-fleet-scout.git
cd aws-fleet-scout
pip install -e .

Quick Start

Interactive Mode (Easiest!)

Launch the interactive menu for a guided experience:

aws-fleet-scout interactive

Compare All Procurement Methods

# Compare spot, capacity blocks, and on-demand
aws-fleet-scout compare --instance-type p4d.24xlarge

# Compare with multiple instances
aws-fleet-scout compare --instance-type p4d.24xlarge --count 4

# Auto-discover all P-series GPU instances
aws-fleet-scout compare --discover-p-series --regions us-east-1,us-west-2

# Auto-discover by instance family prefix
aws-fleet-scout compare --discover g5 --regions us-east-1
aws-fleet-scout compare --discover m7i,c7i,r7i --regions us-east-1

Spot Instance Commands

# Check spot placement scores
aws-fleet-scout spot score --instance-type p5.48xlarge --target-capacity 15

# Use wildcards for regions
aws-fleet-scout spot score --instance-type p5.48xlarge --regions "us-*"

# Auto-discover all P-series and check scores
aws-fleet-scout spot score --discover-p-series --regions us-east-1

Find Best Region for Fleet

# Mixed instance fleet (Ray/Slurm/HPC)
aws-fleet-scout fleet pack --job-spec '{"m7i.4xlarge": 20, "p5.48xlarge": 2}'

Capacity Blocks

# Find reserved GPU capacity
aws-fleet-scout capacity find --instance-type p5.48xlarge --duration 1

# View availability calendar
aws-fleet-scout capacity calendar --instance-type p4d.24xlarge --window 7 --duration 1

Configuration

AWS Credentials

Set AWS credentials:

export AWS_ACCESS_KEY_ID=your_key
export AWS_SECRET_ACCESS_KEY=your_secret
export AWS_DEFAULT_REGION=us-east-1

Or use AWS CLI:

aws configure

Caching

AWS Fleet Scout caches reference data locally to improve performance:

Cache Location (platform-specific):

  • macOS: ~/Library/Caches/aws-fleet-scout/
  • Linux: ~/.cache/aws-fleet-scout/
  • Windows: C:\Users\<user>\AppData\Local\aws-fleet-scout\Cache\

What's Cached:

  • Quota codes (7 days TTL)
  • vCPU counts per instance type (7 days TTL)
  • Instance type offerings per region (7 days TTL)
  • Current quota values (1 hour TTL)
  • AWS region mapping (30 days TTL)
  • Spot placement scores (10 minutes TTL)

Development Workflow (Pixi)

This repository uses Pixi as the single development workflow manager.

Prerequisites

Setup

pixi install

Common Commands

# Run unit tests
pixi run test

# Run all tests
pixi run test-all

# Run functional tests only (requires AWS credentials)
pixi run test-functional

# Lint + type check + unit tests
pixi run check

# Build package artifacts
pixi run build

# Show CLI help
pixi run cli-help

Versioning

Current version comes from aws_fleet_scout/__init__.py.

# Show current version
pixi run version-current

# Bump next release version
pixi run bump-patch
pixi run bump-minor
pixi run bump-major

Documentation

Packaging and Publishing

  • TestPyPI workflow: .github/workflows/publish-testpypi.yml
  • PyPI workflow: .github/workflows/publish-pypi.yml

Both workflows use GitHub Actions with trusted publishing.

Metadata

Release files for aws-fleet-scout 1.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aws-fleet-scout 1.0.2
File Size Uploaded
aws_fleet_scout-1.0.2.tar.gz 68.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for aws-fleet-scout 1.0.2
File Interpreter ABI Platform
aws_fleet_scout-1.0.2-py3-none-any.whl Python 3 none any Details

Total release size: 119.4 kB

Release files / aws_fleet_scout-1.0.2.tar.gz

Download URL aws_fleet_scout-1.0.2.tar.gz
Size 68.2 kB
Tags Source
SHA-256 checksum
How to use checksums
898dd43aa4630de94dcda3c94006b549bfc662fb89ba4f9ec7b1665eba1cbd72
BLAKE2b-256 checksum
How to use checksums
851658801c4a06c524dcd76530c861f801a9785432bf65ea66fb2d4725730dd6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 22, 2026.

Transparency log

Release files / aws_fleet_scout-1.0.2-py3-none-any.whl

Download URL aws_fleet_scout-1.0.2-py3-none-any.whl
Size 51.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d633db0f87ba7841bcfc2d3f7eb2ecf0e14c33e6ec63a6c862780484180fc0fc
BLAKE2b-256 checksum
How to use checksums
b4cbecada9f389e4e20bd7a3d29c7903cc96f667f4b7ec863e1ef721347c9e98
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 22, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.2 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page