imbi-plugin-aws
AWS provider for Imbi under Plugin Architecture v3. The package ships a
single AWSPlugin (slug aws) that backs an AWS Integration with three
capabilities from one credential blob.
Capabilities
This package ships one Plugin, discovered by the imbi-common registry
via the imbi_plugin_* naming convention (module-level PLUGIN
attribute; no imbi.plugins entry points).
| Capability | Contract | Backing service |
|---|---|---|
identity |
IdentityCapability |
IAM Identity Center (device flow) |
logs |
LogsCapability |
CloudWatch Logs Insights |
configuration |
ConfigurationCapability |
SSM Parameter Store |
The identity capability federates each Imbi user into AWS via IAM
Identity Center (formerly AWS SSO) and mints short-lived STS credentials
per call. It is project_scoped=False (Integration-wide) and
default_enabled=True — for AWS, identity is the credential mechanism.
The logs and configuration capabilities set requires_identity=True
and consume those STS credentials transparently.
Manifest shape
Integration-level (declared once, read from ctx.integration_options):
region— default AWS region for every capability; a per-environmentAwsAccount.default_regionoverrides it.default_role_name— IAM role assumed when a per-environmentAwsAccountbinding does not specify one.
Credentials (the only credential declaration, IAM IC auto-managed):
client_id, client_secret, client_scopes.
Capability options (read from ctx.capability_options):
identity:start_url(required),default_account_id.logs:log_group_names(required),base_filter,message_field,timestamp_field,level_field,poll_interval_ms,timeout_seconds.configuration:path_prefix(required),kms_key_id,timeout_seconds.
Identity consumption contract
When the identity capability's materialize() runs (host-side, before
a data capability's handler), it calls GetRoleCredentials against the
IAM IC Portal API and returns short-lived STS keys in
IdentityCredentials.extra:
IdentityCredentials(
access_token=<unchanged IAM IC token>,
extra={
'aws_access_key_id': 'AKIA...',
'aws_secret_access_key': '...',
'aws_session_token': '...',
'aws_region': 'us-east-1',
'aws_account_id': '111111111111',
},
)
The host attaches this to PluginContext.identity; the logs and
configuration capabilities read the five well-known keys from
ctx.identity.extra via aws_session.resolve_credentials(). The account
and role are resolved per environment via
(:Environment)-[:MAPS_TO]->(:AwsAccount), falling back to the
Integration-level default_role_name and region.
License
BSD-3-Clause.
Release files for imbi-plugin-aws 2.26.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 | |
|---|---|---|---|
| imbi_plugin_aws-2.26.0.tar.gz | 49.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| imbi_plugin_aws-2.26.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.7 kB
Release files / imbi_plugin_aws-2.26.0.tar.gz
| Download URL | imbi_plugin_aws-2.26.0.tar.gz |
|---|---|
| Size | 49.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a5a29e90d616003b814d589aa6b3c63991cea54da8868eb89ba73e88cad2451
|
|
BLAKE2b-256 checksum How to use checksums |
968ea95b72abf12550fcedc07f0e2fb32a7812ca111fd5a5c46288658ba2b45c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 19, 2026.
Transparency logRelease files / imbi_plugin_aws-2.26.0-py3-none-any.whl
| Download URL | imbi_plugin_aws-2.26.0-py3-none-any.whl |
|---|---|
| Size | 39.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
579e73ac2617a01198e02e538aaa4a81c62c65fca46dab57b67f84e80b71d0af
|
|
BLAKE2b-256 checksum How to use checksums |
596d7ac0d87852780b9e6fda86fd69726370e5b7d117f34b95440ce0b46cf2b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 19, 2026.
Transparency log
