AWS S3
Let agents read and write files in your Amazon S3 buckets.
Connect it with: API key. AWS S3's own documentation: https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html.
What agents can do
Connect AWS S3 so the agents working your tasks can reach it. With it connected, they can:
- Read a file from a bucket, such as an export, a log or a fixture, and use it in the task.
- Upload a build artifact, a report or a generated dataset to a bucket.
- List what is in a bucket or prefix to find the newest file.
- Check a bucket's policy, versioning or lifecycle settings while debugging.
Before you start
- An AWS account and an IAM user for agents (not the root user).
- An IAM policy on that user allowing s3:ListAllMyBuckets (the Test needs it) plus the bucket actions agents need, for example s3:GetObject and s3:PutObject on arn:aws:s3:::my-bucket/*.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with AWS S3
Jaah connects to AWS S3 with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- Access key ID: AWS console > IAM > Users > the agents' user > Security credentials > Access keys > Create access key; choose Application running outside AWS and copy the Access key ID.
- Secret access key: Shown once, beside the access key ID, when the key is created; download the .csv if you need to keep it.
- Region (optional): The region of the buckets agents use most, for example eu-west-1 (shown on each bucket in the S3 console).
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the AWS S3 card.
- Name the secret and choose who can use it.
- Fill in Access key ID, Secret access key, Region.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to AWS S3 with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah calls AWS S3's API once (GET https://s3.amazonaws.com/) with the stored values, and shows whether AWS S3 accepted it, or which value AWS S3 refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: access_key_id, secret_access_key, region.
Tell the agent in your task description which secret to use, for example “use the AWS S3 secret org/aws-s3”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at AWS S3 once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at AWS S3's side too, revoke or delete the key at AWS S3.
Limitations
- Jaah tests by listing your buckets (ListBuckets). A user whose policy does not allow s3:ListAllMyBuckets fails the Test with a 403 even if it can read a bucket.
- Only long-lived IAM access keys are supported. Temporary (STS) session credentials and IAM Identity Center sign-in are not.
- The Test signs for us-east-1, the global S3 endpoint. An account whose service control policy denies us-east-1 fails the Test.
- Agents can do only what the connected AWS S3 account allows.
Troubleshooting
Test says AWS S3 rejected the secret access key (403)
Either the key pair is wrong or deactivated (check IAM > Users > Security credentials, and create a new key if needed), or the user lacks s3:ListAllMyBuckets. Add that action to the user's policy.
Test says the access key ID cannot be sent
Paste only the 20-character access key ID, starting AKIA, with no spaces or quotes.
Agents get AccessDenied on one bucket
Allow the needed actions on that bucket in the user's IAM policy, and check the bucket policy does not deny the user.
Still stuck? Select Test and read the result: it names the value AWS S3 refused and the status it answered.
FAQ
Can I limit agents to one bucket?
Yes. Allow s3:ListAllMyBuckets for the Test and grant object actions only on that bucket's ARN.
Does it work with S3-compatible storage such as R2 or MinIO?
No. This card is for Amazon S3; use a custom connector for other storage.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one AWS S3 account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.