Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Integration guide

How to Connect Amazon S3 to Apragya, Step by Step

For IT admins and finance teams: set up a bucket, a limited access key and a tested connection, then send the first document from a workflow.

An IT consultant fitting a key into a small lockbox in a server room

To connect Amazon S3 to Apragya you need four things: a bucket, an access key limited to that bucket, the bucket's region, and a few minutes to test. The same steps work for S3-compatible stores such as MinIO, Wasabi, Backblaze B2 and DigitalOcean Spaces.

Most setup problems come from permissions that are too broad or too narrow, or from the wrong region. The steps below avoid both.

After the steps, this page shows an illustrative example from Ahmedabad and what to check once the connection is live.

How to connect Amazon S3 to Apragya

Create the bucket first, in the region you want the data to live in, with public access blocked. Then create a dedicated user or role for Apragya with a policy that allows listing the bucket and reading, writing and deleting objects in it, and nothing else.

Create an access key for that user. In Apragya, add an Amazon S3 connection with the region, the default bucket and the key. Leave the custom endpoint blank for AWS; fill it in only for an S3-compatible store.

  1. Create the bucket in your chosen region.
  2. Create a user with access to that bucket only.
  3. Generate an access key and secret for that user.
  4. Add the S3 connection with region, default bucket and key.
  5. Run the connection test and fix any error it reports.
  6. Add an upload step to a workflow and send a test file.

An example: an Ahmedabad chemicals trader's first connection

Take an illustrative trader whose IT consultant set up an S3 bucket for sales documents. The first test failed, and the fix took five minutes because the error said exactly what was wrong.

The first connection, checked item by item

  • Bucket createdIn the Mumbai region, with public access blocked.Done
  • Access keyFor a user limited to that one bucket.Ready
  • Region on connectionEntered as the default US region at first.Mismatch
  • Test callBucket reachable after the region was fixed.Checked
  • First uploadA test invoice written by a workflow step.Done
The region mismatch was the only problem, and the test call pointed straight at it.

Once the region matched, the test reported the bucket as reachable. The consultant added an upload step to the invoice workflow and watched the first file land in the bucket before handing over.

Five tokens in a row with one turned to face the right way beside a compass
One setting pointed the wrong way, and fixing it made the whole row line up.

Mistakes that make S3 connections fail

Root or admin keys

A key with access to everything is a risk if it leaks.

Wrong region

The bucket is in one region and the connection says another.

Missing list permission

Uploads work but listing a folder fails.

Keys never rotated

An old key stays active long after staff move on.

What happens after you connect Amazon S3

Step 1 of 5

Secrets encrypted

The secret key is stored encrypted and not shown again.

  1. Secrets encrypted: The secret key is stored encrypted and not shown again.
  2. Steps available: Workflows can upload, fetch, list and delete objects.
  3. Calls logged: Each call is recorded against the connection.
  4. Errors explained: AI can explain a failed call in plain language.
  5. Access by role: Only permitted roles can change the connection.

S3 setup options for an Amazon S3 connection

There is more than one way to give Apragya access. The safest is a dedicated user with a policy for one bucket, and a key you rotate on a schedule.

Access choices, compared

FeatureCommon shortcutApragya recommended set-up
IdentityAn admin user's keyA dedicated user for Apragya
ScopeAll bucketsOne bucket, list, read, write, delete
Default bucketLeft blankSet, so the test checks it
RotationNeverOn a schedule, then update the connection

Checked against public information on 16 September 2026.

Why teams choose this S3 bucket integration

Any S3-compatible store

Set a custom endpoint for MinIO, Wasabi, B2 or Spaces.

Temporary credentials

An optional session token is supported.

Documents from records

Files come from the same records every app shares.

On-premise stores

A Tenant Runner can reach a store inside your network.

Reads as well as writes

Pick up files other systems drop into a prefix.

AI on the documents

Agents can work on the same documents, with human review.

Read the Amazon S3 integration overview and document upload.

After the connection works

  1. Add an upload step to one workflow.
  2. Choose a folder and file naming pattern.
  3. Check the call history after a week.
  4. Set a reminder to rotate the access key.

Keep the bucket's own retention and encryption settings under your AWS policies.

What it costs to start

Free
Up to 3 users
CRM, HR and Vendor Onboarding
INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus a choice of apps
INR 7,999
Pro, a month
Up to 25 users and every enterprise app

Connecting Amazon S3, answered

What if the test says access denied?
Check that the user's policy covers the bucket and the actions the workflow needs.
What if the endpoint is unreachable?
For AWS, leave the endpoint blank. For other stores, check the URL and that it is reachable.
Can we connect more than one bucket?
Yes. Steps can name a bucket, or you can add separate connections.
Do we need a default bucket?
No, but setting one lets the test check that exact bucket.
What does it cost to start?
The free plan covers up to 3 users with CRM, HR and Vendor Onboarding and 1,000 AI Credits a month. Starter is INR 3,999 a month for up to 10 users, with CRM and HR plus a choice of apps such as Sales and POS, Inventory, Payroll, Purchase and Payables, Support and Manufacturing. Pro is INR 7,999 a month for up to 25 users with every enterprise app, including Finance and Accounting, plus 5,000 AI Credits, single sign-on and audit logs.

Connect your bucket in ten minutes

Create a limited key, add the connection and send one test document.