Skip to main content

capo-auto-scaling-plans: typed, async Python SDK for AWS Auto Scaling Plans

capo-auto-scaling-plans is a typed Python SDK for AWS Auto Scaling Plans. It has an async client, AsyncAutoScalingPlansClient, for asyncio and trio, and a sync client, AutoScalingPlansClient, with the same methods. Requests and responses are typed with TypedDicts, so your editor and type checker know every field.

It is part of capo, a community-driven alternative to boto3 and aioboto3, built on its own HTTP stack instead of botocore and generated from the official AWS Smithy models. Documentation: https://capo-sdk.dev/services/auto-scaling-plans/

Installation

pip install capo-auto-scaling-plans

Usage

from capo_auto_scaling_plans import AsyncAutoScalingPlansClient


async def main():
    async with AsyncAutoScalingPlansClient() as auto_scaling_plans:
        # Example: call the create_scaling_plan operation
        response = await auto_scaling_plans.create_scaling_plan()
        print(response["scaling_plan_version"])

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_auto_scaling_plans import AsyncAutoScalingPlansClient
from capo_auto_scaling_plans.error import ConcurrentUpdateException


async def main():
    async with AsyncAutoScalingPlansClient() as auto_scaling_plans:
        try:
            await auto_scaling_plans.create_scaling_plan()
        except ConcurrentUpdateException as e:
            print(f"Error: {e}")
            print(e.data)  # additional error data

Retrying

The SDK retries failed operations automatically. Retry behaviour follows the Smithy specification: errors are retried based on their is_retryable and is_throttling_error attributes. Throttling errors use a longer base delay. Network-level failures (connection errors and timeouts) are also retried. Non-retryable errors, such as client errors without the @retryable trait, are raised immediately without further attempts.

The number of attempts defaults to 3 and can be changed at the client level via retry_max_attempts, or per call via config_overrides.

from capo_auto_scaling_plans import AsyncAutoScalingPlansClient


async def main():
    async with AsyncAutoScalingPlansClient() as auto_scaling_plans:
        # Default: 3 attempts for every operation
        response = await auto_scaling_plans.create_scaling_plan()

        # Override per operation
        response = await auto_scaling_plans.create_scaling_plan(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await auto_scaling_plans.create_scaling_plan(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-auto-scaling-plans 0.10.0

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

Source distribution (sdist)

Source distribution for capo-auto-scaling-plans 0.10.0
File Size Uploaded Provenance
capo_auto_scaling_plans-0.10.0.tar.gz 80.6 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-auto-scaling-plans 0.10.0
File Interpreter ABI Platform
capo_auto_scaling_plans-0.10.0-py3-none-any.whl Python 3 none any Details

Total release size: 206.6 kB

Release files / capo_auto_scaling_plans-0.10.0.tar.gz

Download URL capo_auto_scaling_plans-0.10.0.tar.gz
Size 80.6 kB
Tags Source
SHA-256 checksum
How to use checksums
e31bf93c6858e1a7b7e79f95a48ce489642c10856d422bae652ffcbe667d93f7
BLAKE2b-256 checksum
How to use checksums
a692fb16c65798130ae4c7f240fe526c6a80ceaac3dc70406cc40c3c599d8241
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / capo_auto_scaling_plans-0.10.0-py3-none-any.whl

Download URL capo_auto_scaling_plans-0.10.0-py3-none-any.whl
Size 126.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ef2f2798106d7fd75b83415e4b2e92b0f8b5e83b39f188c4fbc1d6104be5541f
BLAKE2b-256 checksum
How to use checksums
a2d30748d064d02f68cffbead32030d84cc1311bae1220a5d610de94d560564e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for capo-auto-scaling-plans 0.10.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

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