Amazon S3 API Integration
Secure object storage with pre-signed upload URLs for documents and media.
What Amazon S3 API integration does
Almost every flow on this site produces a document that has to live somewhere durable and access-controlled — a KYC artefact, a signed agreement, a compliant invoice, a shipping label. S3 is the default answer, and the part worth getting right is how files get into it.
Our integration uses pre-signed upload URLs so files move directly from the client to the bucket without streaming through your application tier. That removes upload bandwidth and latency from your servers entirely while keeping you in control of who may upload what and for how long, because the URL is short-lived and scoped. Server-side encryption, versioning and lifecycle rules are configured to match your retention obligations, which matters when the objects in question are KYC records with a mandated retention period.
What teams build with it
Direct-to-storage uploads
Issue pre-signed URLs so documents and media upload straight to S3, bypassing your API tier.
Compliant document retention
Store KYC artefacts, signed agreements and invoices with encryption, versioning and lifecycle rules matching your obligations.
Secure document delivery
Serve documents through short-lived signed URLs rather than public objects.
Media and asset storage
Hold product images, verification photographs and generated documents at scale.
Endpoints included
POST/aws/v1/s3/presignReturns a time-limited URL to upload an object directly to S3.
Try it in the sandbox
https://sandbox.aeologic.io/aws/v1/s3/presign{
"bucket": "aeo-client-docs",
"key": "kyc/AEO-88213.pdf",
"expires_in": 900,
"content_type": "application/pdf"
}What you need before we start
- An AWS account and a bucket you control
- IAM policies scoped to the connector's required actions
- A retention and lifecycle policy for each document class
- Encryption requirements — SSE-S3 or KMS
How we deliver it
- Bucket structure and IAM policy design
- Pre-signed URL flow implementation for upload and download
- Lifecycle and encryption configuration to your retention policy
- Production rollout with access logging
Related Cloud & Collaboration integrations
Amazon S3 API integration — FAQs
Can we use our own AWS account?
Yes, and it is the recommended setup. The connector operates against your bucket under your IAM policies, so data never leaves your account.
Why pre-signed URLs rather than proxying uploads?
Proxying large files through your application tier wastes bandwidth and makes upload latency your problem. Pre-signed URLs let the client talk to storage directly while you keep control of who may upload what, and for how long.
How is retention handled?
Through S3 lifecycle rules configured per document class to match your obligations, which matters most for KYC artefacts with mandated retention periods.
Ship Amazon S3 in days
Tell us your stack and we'll wire up Amazon S3 API integration for your team.
Talk to Aeologic