Skip to main content

Getting Started

Installation

pip install capo-ssm-incidents

Usage

from capo_ssm_incidents import AsyncSSMIncidentsClient


async def main():
    async with AsyncSSMIncidentsClient() as ssm_incidents:
        # Example: call the batch_get_incident_findings operation
        response = await ssm_incidents.batch_get_incident_findings()
        print(response["findings"])

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_ssm_incidents import AsyncSSMIncidentsClient


async def main():
    async with AsyncSSMIncidentsClient() as ssm_incidents:
        # Example: paginate over get_resource_policies
        async for item in ssm_incidents.iter_get_resource_policies():
            print(item)

Error Handling

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

from capo_ssm_incidents import AsyncSSMIncidentsClient
from capo_ssm_incidents.error import AccessDeniedException


async def main():
    async with AsyncSSMIncidentsClient() as ssm_incidents:
        try:
            await ssm_incidents.batch_get_incident_findings()
        except AccessDeniedException 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_ssm_incidents import AsyncSSMIncidentsClient


async def main():
    async with AsyncSSMIncidentsClient() as ssm_incidents:
        # Default: 3 attempts for every operation
        response = await ssm_incidents.batch_get_incident_findings()

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

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

Metadata

Release files for capo-ssm-incidents 0.8.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-ssm-incidents 0.8.0
File Size Uploaded Provenance
capo_ssm_incidents-0.8.0.tar.gz 115.6 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-ssm-incidents 0.8.0
File Interpreter ABI Platform
capo_ssm_incidents-0.8.0-py3-none-any.whl Python 3 none any Details

Total release size: 367.4 kB

Release files / capo_ssm_incidents-0.8.0.tar.gz

Download URL capo_ssm_incidents-0.8.0.tar.gz
Size 115.6 kB
Tags Source
SHA-256 checksum
How to use checksums
587f843b92c62dc033df5f9da2b47e90e56fa03b7f66ce3c6ac284f13090bea1
BLAKE2b-256 checksum
How to use checksums
346ab97c2167cb49c7c541e3fa42d081ea26ebaa4716583de826836c6ce5f761
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_ssm_incidents-0.8.0-py3-none-any.whl

Download URL capo_ssm_incidents-0.8.0-py3-none-any.whl
Size 251.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
11749dc4d0d4e8af1b90d68d21a6450c567295e66511785b08f1ef8c23c95fa9
BLAKE2b-256 checksum
How to use checksums
0de1443f82f44a3a06f01eb09e088b4308597c42a261fb6734e4d145db06f0d1
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-ssm-incidents 0.8.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