Skip to main content
Rosie.run Docs
S3 Sidekick
All apps ROSI ROSI-LTS Dacx Arlet IYERIS CONV2 S3 Sidekick Zinnia Ballad Blueshift Soon Rosie SSH Soon DriverHub
Search documentation ⌘K
On this page
S3 Sidekick

S3 Sidekick

Fix an S3 Sidekick connection

Check endpoint, region, credentials, permissions, and network errors in S3 Sidekick.

Symptom

An S3 Sidekick connection cannot list a bucket, authenticate, or start a transfer.

Check

Verify the endpoint URL, region, bucket name, access key, secret key, and network route. Confirm that the key has the required bucket permissions and that the provider accepts the addressing mode you selected.

Resolution

  1. Edit the connection and correct one field at a time.
  2. Test the connection after saving the change.
  3. Check the provider status page and local firewall or VPN when the request times out.
  4. Re-enter a rotated key and remove the old credential from the saved connection.
  5. Retry a transfer only after a bucket listing succeeds.

Expected result

The connection lists the intended bucket and a small test action succeeds. A successful connection still exposes only the permissions granted by the provider.

Escalation

Include the provider, package version, endpoint hostname, region, and error code. Never send a secret key, session token, or full authorization header.