Skip to main content

Getting Started

Installation

pip install capo-cloudwatch

Usage

from capo_cloudwatch import AsyncCloudWatchClient


async def main():
    async with AsyncCloudWatchClient() as cloud_watch:
        # Example: call the associate_dataset_kms_key operation
        response = await cloud_watch.associate_dataset_kms_key()
        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_cloudwatch import AsyncCloudWatchClient


async def main():
    async with AsyncCloudWatchClient() as cloud_watch:
        # Example: paginate over describe_alarm_history
        async for item in cloud_watch.iter_describe_alarm_history():
            print(item)

Waiters

Waiters poll an operation until a resource reaches a desired state. If the operation supports waiters it will have a wait_until_ prefixed method.

from capo_cloudwatch import AsyncCloudWatchClient


async def main():
    async with AsyncCloudWatchClient() as cloud_watch:
        # Example: wait for alarm_mute_rule_exists
        await cloud_watch.wait_until_alarm_mute_rule_exists(max_wait_time=300)

Error Handling

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

from capo_cloudwatch import AsyncCloudWatchClient
from capo_cloudwatch.error import ConflictException


async def main():
    async with AsyncCloudWatchClient() as cloud_watch:
        try:
            await cloud_watch.associate_dataset_kms_key()
        except ConflictException 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_cloudwatch import AsyncCloudWatchClient


async def main():
    async with AsyncCloudWatchClient() as cloud_watch:
        # Default: 3 attempts for every operation
        response = await cloud_watch.associate_dataset_kms_key()

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

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

Metadata

Release files for capo-cloudwatch 0.20.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-cloudwatch 0.20.0
File Size Uploaded Provenance Actions
capo_cloudwatch-0.20.0.tar.gz 282.0 kB Without provenance Details for capo_cloudwatch-0.20.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for capo-cloudwatch 0.20.0
File Interpreter ABI Platform Actions
capo_cloudwatch-0.20.0-py3-none-any.whl Python 3 none any Details for capo_cloudwatch-0.20.0-py3-none-any.whl

Total release size: 855.9 kB

Release files / capo_cloudwatch-0.20.0.tar.gz

Download URL capo_cloudwatch-0.20.0.tar.gz
Size 282.0 kB
Tags Source
SHA-256 checksum
How to use checksums
85e67f4e238e0aae2e6e36c95439da8761d7a08613ee4694807e1d36ef788655
BLAKE2b-256 checksum
How to use checksums
94a28b916dfefe7433e37b96c603310a6ed2ada92a24f1bfd7c5abfebda79d0f
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_cloudwatch-0.20.0-py3-none-any.whl

Download URL capo_cloudwatch-0.20.0-py3-none-any.whl
Size 573.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
805600e3bf007e40a3dada1f0d195f0168425c96c09a39ca4493ce3ca7d309e0
BLAKE2b-256 checksum
How to use checksums
e72df6acbd04cc1d050c02e315ed50d124ffa8cbf1f7f046aec6946aeca6e08d
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-cloudwatch 0.20.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