AWS
Call AWS APIs (S3, Lambda, CloudWatch and more) with an IAM access key.
Connect it with: API key. AWS's own documentation: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html.
What agents can do
Connect AWS so the agents working your tasks can reach it. With it connected, they can:
- Read and write objects in the S3 buckets a task names.
- Read CloudWatch logs and metrics to investigate an incident.
- Invoke a Lambda function or inspect resources with the AWS CLI or SDK.
- Anything else the IAM user's policies allow, through the AWS CLI or an SDK in the agent's session.
Before you start
- An AWS account and permission to create an IAM user and access key (IAM > Users).
- An IAM user for Jaah with only the policies agents need. Do not use the root user's keys.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with AWS
Jaah connects to AWS 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 user agents act as > Security credentials > Access keys > Create access key: choose Application running outside AWS, then copy the Access key ID.
- Secret access key: Shown once, on the same Retrieve access keys screen as the Access key ID: copy it before closing, or create a new key.
- Session token (optional): Only for temporary credentials (an assumed role or aws sts get-session-token, keys starting ASIA); leave blank for an IAM user's long-term key.
- Region (optional): The region agents should start from, such as us-east-1 or eu-west-1: the code at the top right of the AWS console.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the AWS card.
- Name the secret and choose who can use it.
- Fill in Access key ID, Secret access key, Session token, 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 with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah makes one read-only call to AWS with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
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, session_token, region.
Tell the agent in your task description which secret to use, for example “use the AWS secret org/aws”.
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 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's side too, revoke or delete the key at AWS.
Limitations
- AWS has no sign-in button for apps like Jaah: you connect with an access key.
- Agents get exactly the IAM user's permissions: scope its policies to the buckets, functions and logs tasks need.
- Temporary (session) credentials expire, usually within 1 to 12 hours; replace them or use a long-term key for a lasting connection.
- Agents can do only what the connected AWS account allows.
Troubleshooting
Test says AWS rejected the request (403, InvalidClientTokenId or SignatureDoesNotMatch)
The access key ID or secret is wrong, deactivated or deleted. Create a new access key in IAM and select Replace.
Test says the request is time-skewed
The Jaah server's clock is wrong, not your key. Tell your Jaah operator.
Test passes but agents get AccessDenied
The IAM user lacks a policy for that action. Attach a policy that allows it in IAM > Users > Permissions.
A temporary credential stops working after a few hours
Its session expired. Paste a fresh key, ID and session token, or use an IAM user's long-term key.
Still stuck? Select Test and read the result: it names the value AWS refused and the status it answered.
FAQ
Does the test need any IAM permission?
No. Jaah calls STS GetCallerIdentity, which every valid key may call, and shows the account and ARN it answered for.
Is this the same secret Jaah uses to launch cloud nodes?
It is the same kind of secret. A separate secret per use keeps permissions tight.
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 account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.