Get your keys
- In the AWS console, open IAM and pick (or create) a user for yourself.
- Under Security credentials, create an access key for CLI/third-party use.
- Copy the Access Key ID and Secret Access Key.
Give the user only the S3 permissions it needs. A practical starting policy allows s3:ListAllMyBuckets plus full access to the specific buckets you work with; avoid attaching account-wide admin just to browse files.
Connect
- Add a new connection and choose the Amazon S3 preset.
- Paste the keys. If you already use the AWS CLI, the app can also import the profiles from your existing AWS config files instead.
- Connect. The app resolves each bucket’s region automatically, so buckets from every region show up in one connection.
Good to know
- No endpoint to type: the preset uses AWS’s regional endpoints automatically and follows each bucket to its home region.
- Storage classes are visible in the file table. Objects in Glacier classes need a restore before download; standard and infrequent-access classes download directly.
- The app’s versioning browser, lifecycle editor, policy editor and CORS editor map to the same S3 features you would otherwise manage in the AWS console.
- Share links that expire respect your IAM permissions and work for specific object versions too.