Genkit AWS Plugin
AWS observability integration for Genkit, enabling telemetry export to AWS X-Ray (distributed tracing) and CloudWatch (metrics/logs).
Installation
pip install genkit-plugin-aws
Quick Start
from genkit.plugins.aws import add_aws_telemetry
# Enable AWS X-Ray telemetry (uses AWS_REGION env var)
add_aws_telemetry()
# Or with explicit region
add_aws_telemetry(region='us-west-2')
Configuration
Environment Variables
| Variable | Description |
|---|---|
AWS_REGION |
AWS region for X-Ray endpoint (required) |
AWS_DEFAULT_REGION |
Fallback region if AWS_REGION not set |
AWS_ACCESS_KEY_ID |
AWS access key (or use IAM role) |
AWS_SECRET_ACCESS_KEY |
AWS secret key (or use IAM role) |
Options
add_aws_telemetry(
region='us-west-2', # AWS region (or use AWS_REGION env var)
log_input_and_output=False, # Set True to disable PII redaction
force_dev_export=True, # Export even in dev environment
disable_traces=False, # Set True to disable tracing
)
IAM Permissions
The following IAM permissions are required:
For Traces (X-Ray)
Attach the AWSXrayWriteOnlyPolicy managed policy, or create a custom policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"xray:PutTraceSegments",
"xray:PutTelemetryRecords"
],
"Resource": "*"
}
]
}
Architecture
┌─────────────────────────────────────────────────────────────────────────┐
│ AWS Plugin │
├─────────────────────────────────────────────────────────────────────────┤
│ Plugin Entry Point (__init__.py) │
│ └── add_aws_telemetry() - Enable X-Ray/CloudWatch export │
├─────────────────────────────────────────────────────────────────────────┤
│ telemetry/tracing.py - Distributed Tracing │
│ ├── AWS X-Ray OTLP exporter configuration │
│ ├── SigV4 authentication for AWS endpoints │
│ ├── AwsXRayIdGenerator for X-Ray-compatible trace IDs │
│ └── OpenTelemetry integration │
└─────────────────────────────────────────────────────────────────────────┘
Data Flow:
┌──────────────┐ ┌──────────────┐ ┌──────────────────────┐
│ Genkit App │───►│ OpenTelemetry│───►│ AWS Observability │
│ (actions, │ │ SDK + ADOT │ │ (X-Ray, CloudWatch) │
│ flows) │ └──────────────┘ └──────────────────────┘
└──────────────┘
AWS Documentation
License
Apache-2.0
Metadata
Release files for genkit-plugin-aws 0.5.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 | |
|---|---|---|---|
| genkit_plugin_aws-0.5.0.tar.gz | 19.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| genkit_plugin_aws-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.9 kB
Release files / genkit_plugin_aws-0.5.0.tar.gz
| Download URL | genkit_plugin_aws-0.5.0.tar.gz |
|---|---|
| Size | 19.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f92f4d7289dbefb2730452f147dbce468253e1dc09bd3a7a3b597a002275a638
|
|
BLAKE2b-256 checksum How to use checksums |
1bbc0826f9e29f5a1abe52e0bcf38d615effeb0376b1d4c950b7a32d2e347a14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 4, 2026.
Transparency logRelease files / genkit_plugin_aws-0.5.0-py3-none-any.whl
| Download URL | genkit_plugin_aws-0.5.0-py3-none-any.whl |
|---|---|
| Size | 20.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34d9508af4cf6c9e3acd1559df87e127d6f918dadcba2443a02ffe6c2e874c99
|
|
BLAKE2b-256 checksum How to use checksums |
81ef3de85068a088833a6170de2762ce5463719a000b947a916fdd4b37f4ee73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 4, 2026.
Transparency log