Skip to main content

capo-fms: typed, async Python SDK for AWS FMS

capo-fms is a typed Python SDK for AWS FMS. It has an async client, AsyncFMSClient, for asyncio and trio, and a sync client, FMSClient, 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/fms/

Installation

pip install capo-fms

Usage

from capo_fms import AsyncFMSClient


async def main():
    async with AsyncFMSClient() as fms:
        # Example: call the associate_admin_account operation
        response = await fms.associate_admin_account()
        print(response)

Pagination

Some operations in this SDK support pagination. If the operation supports pagination it will have an iter_ prefixed method that returns an async iterator.

from capo_fms import AsyncFMSClient


async def main():
    async with AsyncFMSClient() as fms:
        # Example: paginate over list_admin_accounts_for_organization
        async for item in fms.iter_list_admin_accounts_for_organization():
            print(item)

Error Handling

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

from capo_fms import AsyncFMSClient
from capo_fms.error import InternalErrorException


async def main():
    async with AsyncFMSClient() as fms:
        try:
            await fms.associate_admin_account()
        except InternalErrorException 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_fms import AsyncFMSClient


async def main():
    async with AsyncFMSClient() as fms:
        # Default: 3 attempts for every operation
        response = await fms.associate_admin_account()

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

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

Metadata

Release files for capo-fms 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-fms 0.10.0
File Size Uploaded Provenance
capo_fms-0.10.0.tar.gz 161.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-fms 0.10.0
File Interpreter ABI Platform
capo_fms-0.10.0-py3-none-any.whl Python 3 none any Details

Total release size: 535.4 kB

Release files / capo_fms-0.10.0.tar.gz

Download URL capo_fms-0.10.0.tar.gz
Size 161.8 kB
Tags Source
SHA-256 checksum
How to use checksums
fac7e7d3e32030de48c76aa4a5faf28f3c6c3bb8dea90ad9218dcae016a5ac2d
BLAKE2b-256 checksum
How to use checksums
cc9539b4e475a181c9b506c3d69016d0fd1bbc24650b815f6e5b407bbad063c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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_fms-0.10.0-py3-none-any.whl

Download URL capo_fms-0.10.0-py3-none-any.whl
Size 373.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a542ac814449bf1eddc3db5c260a9cf0268e03a7a8a99eefdc270375157f424c
BLAKE2b-256 checksum
How to use checksums
1eec71323c02379a8db73e3a10ae1040479fe0b3982fed14f63f441c59ff85f2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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-fms 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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