Getting Started
Installation
pip install capo-lambda-microvms
Usage
from capo_lambda_microvms import AsyncLambdaMicrovmsClient
async def main():
async with AsyncLambdaMicrovmsClient() as lambda_microvms:
# Example: call the create_microvm_image operation
response = await lambda_microvms.create_microvm_image()
print(response["image_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_lambda_microvms import AsyncLambdaMicrovmsClient
async def main():
async with AsyncLambdaMicrovmsClient() as lambda_microvms:
# Example: paginate over list_managed_microvm_images
async for item in lambda_microvms.iter_list_managed_microvm_images():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_lambda_microvms import AsyncLambdaMicrovmsClient
from capo_lambda_microvms.error import AccessDeniedException
async def main():
async with AsyncLambdaMicrovmsClient() as lambda_microvms:
try:
await lambda_microvms.create_microvm_image()
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_lambda_microvms import AsyncLambdaMicrovmsClient
async def main():
async with AsyncLambdaMicrovmsClient() as lambda_microvms:
# Default: 3 attempts for every operation
response = await lambda_microvms.create_microvm_image()
# Override per operation
response = await lambda_microvms.create_microvm_image(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await lambda_microvms.create_microvm_image(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-lambda-microvms 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| capo_lambda_microvms-0.4.0.tar.gz | 109.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_lambda_microvms-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 325.7 kB
Release files / capo_lambda_microvms-0.4.0.tar.gz
| Download URL | capo_lambda_microvms-0.4.0.tar.gz |
|---|---|
| Size | 109.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4677f25d0f76051618893a77102b8dbfad99eb666aafb445bce6aadb06fd5c0
|
|
BLAKE2b-256 checksum How to use checksums |
a1f5b62548f626b4c53b74c4bf1f7946f58f71389db33f1b2ff413bdce0fe1eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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_lambda_microvms-0.4.0-py3-none-any.whl
| Download URL | capo_lambda_microvms-0.4.0-py3-none-any.whl |
|---|---|
| Size | 216.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
51956982fe10753591d77e8faffbd602b1b695a89a9ab760215d697e0a594150
|
|
BLAKE2b-256 checksum How to use checksums |
0474442c93e1fd7cab63054e3617a602bed6549747fc49198d16ba927d08ec55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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-lambda-microvms 0.4.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.