datus-aws-common
Shared plumbing for the Datus AWS plugins (datus-glue-plugin,
datus-s3-plugin, datus-cloudwatch-plugin, …). It is not a plugin — it
registers no datus.plugins entry point — but every AWS plugin depends on it
so the boto3 wiring lives in exactly one place.
Extracted once nine AWS plugins needed the same code (the monorepo's "copy small helpers until at least three plugins need them" rule points to extraction well before that).
What it provides
| Module | Contents |
|---|---|
errors |
PluginError/UsageError/ConfigError/MissingDependencyError/ApiError and exit codes 0/1/2/3/8 (copied from datus-airflow-plugin) |
output |
render_rows / render_one — table / plain / json / yaml (copied) |
awsconfig |
AwsSettings (region + credentials + AssumeRole + endpoint/timeout) and validate_keys for strict per-profile key checking |
session |
build_session (profile/keys/chain + optional STS AssumeRole) and build_client (endpoint override + botocore retry/timeout Config) |
client |
call (botocore ClientError/BotoCoreError → ApiError), paginate (boto3 paginators → flat list), wait_until (monotonic-deadline poller for --wait) |
cli |
AwsContext (lazy, multi-service client cache), add_output_option / confirm / parse_json_arg / parse_datetime_arg, and run (parse → dispatch → error-to-exit-code) |
Credential model
Every AWS plugin profile shares the same credential block; resolution mirrors the airflow plugin's S3 deploy:
region: us-east-1
profile: my-aws-profile # or explicit keys / the standard chain
access_key_id: ${AWS_ACCESS_KEY_ID}
secret_access_key: ${AWS_SECRET_ACCESS_KEY}
session_token: ${AWS_SESSION_TOKEN}
role_arn: arn:aws:iam::123456789012:role/datus # short-lived STS AssumeRole
role_session_name: datus # optional
external_id: team-a # optional
endpoint_url: http://minio:9000 # optional (S3-compatible stores)
timeout: 60 # optional botocore connect/read timeout
max_attempts: 3 # optional botocore retry attempts
Development
uv run --package datus-aws-common pytest datus-aws-common
Metadata
Release files for datus-aws-common 0.1.1
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 | Actions |
|---|---|---|---|---|
| datus_aws_common-0.1.1.tar.gz | 12.2 kB | Without provenance | Details for datus_aws_common-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datus_aws_common-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for datus_aws_common-0.1.1-py3-none-any.whl |
Total release size: 23.6 kB
Release files / datus_aws_common-0.1.1.tar.gz
| Download URL | datus_aws_common-0.1.1.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d88ecb50562ad8ac24a683ecbec976895811acc497682844763133b04ded77f1
|
|
BLAKE2b-256 checksum How to use checksums |
547f8a7fcdbfe4f576213a47bd780a92f110cf36ef6238ad60c46d5c7e6828b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / datus_aws_common-0.1.1-py3-none-any.whl
| Download URL | datus_aws_common-0.1.1-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5184497f4f8267477668c40cb89665dfd07381f2f803a9b1c79a2ec1ed50100
|
|
BLAKE2b-256 checksum How to use checksums |
e40225ca92d3139fb5f05dd0755382bd11b0b54c5d1ed0b3daf1037aaa250c0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for datus-aws-common 0.1.1
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.