Skip to content

Connect in Sliick Settings

The last step of S3 setup. You do this once, and again only if you rotate keys.

  1. Open Sliick Settings.
  2. Provider = Amazon S3 (or S3-Compatible / B2 / Wasabi / R2, which use the same form).
  3. Paste Access Key ID, Secret Access Key, Bucket Name, and Region from the AWS setup. Endpoint is optional for standard AWS S3, so leave it blank; for every S3-compatible provider it is required. See S3-compatible providers.
  4. In Integration User, enter the username of the dedicated user you set up in Set up the Integration User. It pre-fills if you have connected before.
  5. Click Connect.

Sliick saves your settings and sets up the credential, then leaves the connection awaiting validation. Once the permission grant in Salesforce setup is in place, click Test connection. On success the status flips to Active. If the running user lacks the principal grant, the test fails inline with a pointer to the permission-set step.

Sliick also registers what large-file uploads need automatically at connect, so there is nothing to allowlist by hand.

Update the Access Key ID and Secret in Sliick Settings and reconnect. There is no second copy to maintain.

All files live under a root folder, Salesforce-Files-<your org id> by default, which keeps each org and sandbox separate when they share a bucket. You can change it, subject to a naming rule and a 50-character limit. See Folders and breadcrumbs.

See Troubleshooting.