BusyBot

Reference · Credentials

AWS credentials

Used by 5 BusyBot nodes.

Type aws 6 fields

The AWS credential holds an access key ID and secret for an IAM identity, plus an optional region, session token and endpoint override. It is used by 5 BusyBot nodes. Because it can point at a custom endpoint with path-style addressing, it also works with S3-compatible providers such as MinIO.

Fields

FieldTypeRequiredNotes
Access Key ID
accessKeyId		 string Yes AWS access key ID
Secret Access Key
secretAccessKey		 password Yes AWS secret access key
Region
region		 string No AWS region (e.g., us-east-1, eu-west-1)
Session Token
sessionToken		 password No Optional STS session token (for temporary credentials)
Custom Endpoint
customEndpoint		 string No Override AWS endpoint for S3-compatible services (e.g., https://nyc3.digitaloceanspaces.com, http://localhost:9000 for MinIO). Leave empty for AWS.
Force Path Style
forcePathStyle		 boolean No Use path-style addressing (required for MinIO and some S3-compatible providers)

Getting your credentials

  1. In the AWS console, open IAM and create a user (or use an existing one) dedicated to this integration.
  2. Attach a policy granting only the permissions the nodes you use actually need — not administrator access.
  3. Create an access key for that user and copy both the Access Key ID and the Secret Access Key. The secret is shown only once.
  4. Set Region to the region your resources live in, for example us-east-1 or eu-west-1.

For temporary credentials from AWS STS, also supply the Session Token; leave it empty for long-lived keys.

Permissions and scopes

Scope the IAM policy to the specific resources and actions in use. An automation credential with broad permissions is a standing risk, and AWS makes narrow policies straightforward.

Prefer short-lived STS credentials where your setup supports them, supplying the session token alongside the key pair.

Troubleshooting

  • SignatureDoesNotMatch — the secret access key is wrong or has whitespace from copying. Regenerate and paste carefully.
  • AccessDenied — the key is valid but the IAM policy does not allow that action on that resource. Widen the policy deliberately rather than granting blanket access.
  • Region errors or resource not found — the region does not match where the resource lives.
  • S3-compatible provider failing — set Custom Endpoint to the provider’s endpoint and enable Force Path Style, which MinIO and several other providers require.

Frequently asked questions

Can I use this with MinIO or another S3-compatible service?

Yes — set Custom Endpoint to the provider's endpoint and turn on Force Path Style, which MinIO and several others require. Note the dedicated S3 node also exists for non-AWS providers.

When do I need the Session Token?

Only with temporary credentials issued by AWS STS. Long-lived IAM access keys do not use one, so leave it empty for those.

What permissions should the IAM user have?

The minimum for the operations you actually run. Scope the policy to specific resources and actions rather than attaching administrator access to an automation identity.

Why do I get AccessDenied when the key works elsewhere?

The key is authenticating fine but the IAM policy does not permit that action on that resource. That is an authorisation problem, not a credential one.

Nodes that use AWS

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.