Amazon S3
The Amazon S3 integration is available today.
Many organizations stage documents and data extracts in Amazon S3. The LORIQ integration ingests files from the storage locations you designate, feeding both the document workspace and data import pipelines.
It is designed for infrastructure-managed file flows — system exports, archival document sets, and scheduled data drops — complementing the end-user document platforms.
Supported data
Ingested from the Amazon S3 locations you designate.
Object listings and content signatures determine what is new or changed, so only deltas are processed.
Security
Every LORIQ integration — including Amazon S3 — runs on one shared, hardened connectivity framework rather than per-integration plumbing:
- Credentials are stored in an encrypted, per-connection vault and are never exposed to browser sessions or logs.
- Every synced record is scoped to your organization — tenant isolation is enforced at the query layer and verified by automated guard tests.
- All incoming files pass malware scanning before storage; unscanned bytes are never persisted (fail-closed by design).
- Imports land as drafts for review — synced data never silently overwrites your records.
- Every sync, import, and connection change is captured in the platform audit trail.
Authentication
LORIQ connects to Amazon S3 using scoped credentials you provision (S3 API (access keys)). We recommend read-only credentials limited to the specific buckets, containers, or paths LORIQ should see.
Credentials are held in LORIQ's encrypted vault and can be rotated or removed at any time; disconnecting purges them immediately.
Setup guide
- 1Provision access
Create scoped, read-only credentials for the Amazon S3 locations LORIQ should read.
- 2Connect
Enter the credentials in Settings → Integrations. LORIQ verifies access before saving the connection.
- 3Preview & sync
Preview what would be ingested, then enable the schedule. Files are scanned and deduplicated on the way in.
Frequently asked questions
Does LORIQ need write access?
No. Read-only access to the designated Amazon S3 locations is sufficient and recommended.
How are large or irrelevant files handled?
Ingestion is scoped to the paths you choose, and every file passes malware scanning and deduplication before storage.
Expanding capabilities
- Event-driven ingestion for lower-latency pickup of new objects.
- Expanded structured-data pipelines so data files can flow directly into financial imports.
See Amazon S3 + LORIQ in action
Walk through the integration with our team and see how your data flows into a single commercial credit workspace.
Request a demo