Skip to main content

interloper-aws

AWS integration for interloper: an S3Destination that stores asset data in an Amazon S3 bucket, and the AWSConnection that holds the credentials.

S3Destination is an ObjectStoreDestination, the same base as the Cloud Storage destination in interloper-google-cloud, so the two behave identically: one object per partition in a hive-partitioned layout, Parquet (the default), JSONL or CSV, the partition column in the path only, and each object's row count stored as row_count user metadata.

s3://{bucket}/{prefix}/{dataset}/{table}/data.{ext}
s3://{bucket}/{prefix}/{dataset}/{table}/{column}={partition}/data.{ext}

Usage

import interloper as il
from interloper_aws import AWSConnection, S3Destination

destination = S3Destination(
    connection=AWSConnection(region="eu-central-1"),
    bucket="acme-lake",
    prefix="raw",
    format="parquet",
)

source = Shop(destinations=destination)

Credentials

The connection takes an access key pair (access_key_id, secret_access_key, plus session_token for temporary credentials) and a region, defaulting to eu-central-1. Each field also loads from the standard environment variables: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN and AWS_REGION.

Leave the key pair empty and boto3's default credential chain applies: environment, shared config files, then the instance or pod role (an EC2 instance profile, EKS IRSA or Pod Identity). In a cluster, that means no stored secret at all: grant the workload's role access to the bucket.

The connection's check calls STS GetCallerIdentity, which needs no IAM permission, so a failing check means the credentials themselves are wrong. The bucket picker calls ListBuckets.

Permissions

The destination needs, on the bucket and its objects:

  • s3:PutObject to write
  • s3:GetObject to read, and to count objects written without row_count metadata
  • s3:ListBucket for partition row counts
  • s3:ListAllMyBuckets for the bucket picker only

Notes

ListObjectsV2 returns no user metadata, so partition row counts issue one HeadObject per listed object. That is still no download: the count comes from the row_count metadata stamped at write time. Objects written by other tools, without that metadata, are downloaded and counted.

Metadata

Release files for interloper-aws 0.131.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 interloper-aws 0.131.0
File Size Uploaded Provenance Actions
interloper_aws-0.131.0.tar.gz 4.8 kB Without provenance Details for interloper_aws-0.131.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for interloper-aws 0.131.0
File Interpreter ABI Platform Actions
interloper_aws-0.131.0-py3-none-any.whl Python 3 none any Details for interloper_aws-0.131.0-py3-none-any.whl

Total release size: 11.2 kB

Release files / interloper_aws-0.131.0.tar.gz

Download URL interloper_aws-0.131.0.tar.gz
Size 4.8 kB
Tags Source
SHA-256 checksum
How to use checksums
91a804600a5c15a43863d90e331e69b9f6c3d74b202f03df00b6323fc2ac6b79
BLAKE2b-256 checksum
How to use checksums
1c45ea1a4ac5117826cc72a16517d993cc68d2b03f578d737c32a9be7c297e67
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","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 / interloper_aws-0.131.0-py3-none-any.whl

Download URL interloper_aws-0.131.0-py3-none-any.whl
Size 6.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
84b9216c0af9dd12ff0fb8e95f2ef7d1e5af4e522166fbd8d0f4f96e693ab05b
BLAKE2b-256 checksum
How to use checksums
ee35d050b31d56a9f84dbb53f622be4bfab30d27f71a8b16029dcd512ee0c196
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","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 interloper-aws 0.131.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.

Release history Release notifications | RSS feed

This release

0.131.0 This release

2 release files No provenance

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