Skip to main content

capo-rum: typed, async Python SDK for AWS RUM

capo-rum is a typed Python SDK for AWS RUM. It has an async client, AsyncRUMClient, for asyncio and trio, and a sync client, RUMClient, 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/rum/

Installation

pip install capo-rum

Usage

from capo_rum import AsyncRUMClient


async def main():
    async with AsyncRUMClient() as rum:
        # Example: call the list_tags_for_resource operation
        response = await rum.list_tags_for_resource()
        print(response["resource_arn"])

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_rum import AsyncRUMClient


async def main():
    async with AsyncRUMClient() as rum:
        # Example: paginate over list_app_monitors
        async for item in rum.iter_list_app_monitors():
            print(item)

Error Handling

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

from capo_rum import AsyncRUMClient
from capo_rum.error import InternalServerException


async def main():
    async with AsyncRUMClient() as rum:
        try:
            await rum.list_tags_for_resource()
        except InternalServerException 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_rum import AsyncRUMClient


async def main():
    async with AsyncRUMClient() as rum:
        # Default: 3 attempts for every operation
        response = await rum.list_tags_for_resource()

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

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

Metadata

Release files for capo-rum 0.9.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-rum 0.9.0
File Size Uploaded Provenance
capo_rum-0.9.0.tar.gz 117.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-rum 0.9.0
File Interpreter ABI Platform
capo_rum-0.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 319.0 kB

Release files / capo_rum-0.9.0.tar.gz

Download URL capo_rum-0.9.0.tar.gz
Size 117.4 kB
Tags Source
SHA-256 checksum
How to use checksums
0627f952d034be86bd324ea387dd2eb4f372f4c1bb1c64b534c8088be628093d
BLAKE2b-256 checksum
How to use checksums
d775901d51ea3f8bc1c41cc038d47e87e92d6f4d70ce12ab4c21e5431d3486e5
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_rum-0.9.0-py3-none-any.whl

Download URL capo_rum-0.9.0-py3-none-any.whl
Size 201.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a2d4115e7195dd08c82a35514e0fe312d6929f3050b90e73f887b03348dc91b1
BLAKE2b-256 checksum
How to use checksums
4b330bbae4d5dcc31e6b1ae24341df7bf1bdb8a49c422a9b92eb309548b03da4
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-rum 0.9.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