Skip to main content

capo-lambda: typed, async Python SDK for AWS Lambda

capo-lambda is a typed Python SDK for AWS Lambda. It has an async client, AsyncLambdaClient, for asyncio and trio, and a sync client, LambdaClient, 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/lambda/

Installation

pip install capo-lambda

Usage

from capo_lambda import AsyncLambdaClient


async def main():
    async with AsyncLambdaClient() as lambda_:
        # Example: call the delete_function operation
        response = await lambda_.delete_function()
        print(response["status_code"])

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_lambda import AsyncLambdaClient


async def main():
    async with AsyncLambdaClient() as lambda_:
        # Example: paginate over list_capacity_providers
        async for item in lambda_.iter_list_capacity_providers():
            print(item)

Streaming Request

Some operations accept a streaming request body. Pass an async iterator of bytes chunks, or the whole body as bytes, for the streaming parameter.

A plain iterator can be sent only once, so if a request fails after its body was transmitted the operation is not retried. To get retries for streamed uploads, pass a Body instead: it wraps a source that can be reopened, and every attempt streams a fresh copy. Body.from_path (sync client) and Body.async_from_path (async client, needs anyio) stream a file from disk; Body(opener) takes any context manager that yields a (stream, length) pair.

from capo_lambda import AsyncLambdaClient, Body


async def main():
    async with AsyncLambdaClient() as lambda_:
        # Example: call invoke_async with a streaming request body
        async def chunks():
            yield b'Hello, World!'

        response = await lambda_.invoke_async(invoke_args=chunks())
        print(response)

        # Or pass the whole body as bytes
        response = await lambda_.invoke_async(invoke_args=b'Hello, World!')
        print(response)

        # Or stream a file with Body: the file is reopened on every retry
        # and Content-Length is taken from its size, so no content_length needed
        response = await lambda_.invoke_async(invoke_args=Body.async_from_path("hello.txt"))
        print(response)

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_lambda import AsyncLambdaClient


async def main():
    async with AsyncLambdaClient() as lambda_:
        # Example: wait for function_exists
        await lambda_.wait_until_function_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_lambda import AsyncLambdaClient
from capo_lambda.error import InvalidParameterValueException


async def main():
    async with AsyncLambdaClient() as lambda_:
        try:
            await lambda_.delete_function()
        except InvalidParameterValueException 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.

retry_mode="adaptive" (or AWS_RETRY_MODE=adaptive, or retry_mode = adaptive in the AWS profile) also slows the whole client down once the service starts throttling it, then speeds back up as requests succeed. The default is standard.

from capo_lambda import AsyncLambdaClient


async def main():
    async with AsyncLambdaClient() as lambda_:
        # Default: 3 attempts for every operation
        response = await lambda_.delete_function()

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

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

Metadata

Release files for capo-lambda 0.29.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-lambda 0.29.0
File Size Uploaded Provenance Actions
capo_lambda-0.29.0.tar.gz 417.1 kB Without provenance Details for capo_lambda-0.29.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for capo-lambda 0.29.0
File Interpreter ABI Platform Actions
capo_lambda-0.29.0-py3-none-any.whl Python 3 none any Details for capo_lambda-0.29.0-py3-none-any.whl

Total release size: 1.3 MB

Release files / capo_lambda-0.29.0.tar.gz

Download URL capo_lambda-0.29.0.tar.gz
Size 417.1 kB
Tags Source
SHA-256 checksum
How to use checksums
42563f1e686988cc2d2df37ca69b00d1cf8853aa2d59151aeac1a2d3d15436c8
BLAKE2b-256 checksum
How to use checksums
b3f777ff9b39400c0092b38660ec46648cf8cfab3eda2e6bf797e1f7dfb8ce04
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / capo_lambda-0.29.0-py3-none-any.whl

Download URL capo_lambda-0.29.0-py3-none-any.whl
Size 874.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0d763f9635085aed4f98a8ffd15cbbc7c683cfe595261383b771b657dc94088f
BLAKE2b-256 checksum
How to use checksums
9abb7d26ecd1377acd4cad16f081d6710b8d1fdf59c177a606b2918a8f65316c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for capo-lambda 0.29.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