Amazon S3 - Auxia Docs

Amazon S3 is AWS’s object storage service. Auxia’s S3 connector copies files from your bucket using read-only access you grant through an IAM bucket policy or role, then maps them into Auxia’s schema. Auxia never writes to your bucket.

Setup guide

Connect in about 15 minutes

Troubleshooting

Fix common errors

Release notes

What’s changed

Features

Feature	Supported	Notes
Self-serve setup	✅	Wizard in the Auxia Console; generates the exact policies for you
AI-assisted schema mapping	✅	Reads your files and proposes a mapping with a confidence level
File formats	✅	Self-serve: Parquet (recommended), CSV, newline-delimited JSON. With the Auxia team: also Avro, ORC, Delta Lake, Iceberg
Date-partitioned folders	✅	Seven folder date formats, or whole-folder snapshots
User ID resolution via joins	✅	Resolve a table’s user ID by joining it to another table
Access via Auxia’s role	✅	One bucket policy — nothing to create in your account
Access via your own IAM role	✅	For teams that need to own and revoke the role
Server-side encryption	✅	SSE-S3 and SSE-KMS. SSE-C is not supported
Incremental sync	Partial	User attribute tables only. Event files sync as daily full refresh
Data Health monitoring	✅	Per-stage status, run history, and row counts
Capture deletes	❌	Files must be append-only
Row filtering	✅	Files are still copied in full; the filter decides what’s read into Auxia
Transfer only	Coming soon	Available for BigQuery today
Edit a connection after creation	Coming soon
Self-serve backfills	Coming soon	Today, request backfills from your Auxia contact

Sync overview

Access: read-only — s3:GetObject and s3:ListBucket on the one bucket you connect, plus kms:Decrypt if the bucket uses SSE-KMS.
Cadence: self-serve connections sync once a day, and a day’s data appears the next morning. Connections set up with the Auxia team can check for new files about every hour. When will my data show up? →
Mode: event files sync as a full refresh of each date folder, so re-runs are always safe. User attribute files sync as new rows only.
Transfer: files are copied into Auxia-side storage with Google Cloud Storage Transfer Service, then mapped into Auxia’s unified tables.

File requirements

The short version — the full rules are in File source requirements:

One folder per table, with every file in a folder sharing one schema.
Date folders such as dt=2026-10-02/ let Auxia read only the newest day.
Append-only: never overwrite or delete a file; write corrections as new files.
CSV needs a header row and comma delimiters.

s3://your-bucket/auxia-export/events/dt=2026-10-02/part-0001.parquet

Limitations

Whole-file compression (.parquet.gz, .csv.gz) and archives (.tar.gz) aren’t supported. Client-side encrypted files (such as PGP) are supported only in limited cases.
Avro, ORC, Delta Lake, and Iceberg need the Auxia team rather than the wizard.
More than about 1 TB per run works, but talk to your Auxia contact before committing to a timeline.
Dates in file names (rather than folder names) aren’t detected.
A new connection doesn’t load history automatically. Contact your Auxia point of contact to load a past date range.
Data in Amazon Redshift, Kinesis, or Kafka can be connected by first unloading or sinking it to S3. See Don’t see your source?

Setup guide

Troubleshooting

Release notes

​Features

​Sync overview

​File requirements

​Limitations

Features

Sync overview

File requirements

Limitations