Most S3 tools were built for engineers moving objects. A team that keeps contracts, spreadsheets, decks and media in S3 needs something different: to open the file, read it, and get on with the work, from a browser, without installing a client or holding AWS credentials.
If you are evaluating a viewer for that job, these are the questions that separate the options.
Which formats does it actually render?
Listing objects is easy. Rendering them is the product. Ask for the list of formats that display in the browser, as opposed to formats that are offered as a download.
- PDF, images, plain text, HTML and Markdown are the baseline.
- Word, Excel and PowerPoint need a conversion service. Ask where that conversion happens.
- HEIC photos, audio and video need transcoding or streaming by range.
- Zip archives should be inspectable without extracting them.
How does it get access to the bucket?
A viewer that asks for an access key and secret is asking you to hand over a long-lived credential. The better pattern is a cross-account IAM role with an external ID, scoped to specific buckets and prefixes, that the vendor assumes for short-lived credentials. You can see exactly what was granted, and you can revoke it by deleting the role.
Where do the file contents go?
A desktop client reads straight from S3 to the laptop. A hosted viewer reads the object on your behalf. Ask whether contents are cached, for how long, and whether any third party is involved in rendering. A trustworthy answer names the exceptions rather than claiming there are none.
Who can do what, and is it recorded?
- Separate viewing from changing. Most people only need to read.
- Risky actions such as delete, extract and restore should require a specific role and a confirmation.
- Every open, share and change should be attributable to a signed-in person, and exportable.
The options, briefly
- The S3 console: complete and free, but built for operators, and every user needs an IAM identity.
- Desktop clients: fast for transfers, but they usually store access keys on each machine and leave no central audit trail.
- Storage Browser for Amazon S3: an AWS-maintained React component for list, upload, download, copy and delete inside your own application. You build the authentication, hosting and any preview.
- A hosted workspace such as BucketDesk: previews, sharing, archive inspection and cold storage restore in a browser, connected by an IAM role.
Where BucketDesk fits
BucketDesk previews PDF, images including HEIC, text, HTML and Markdown on the free Starter plan for one bucket. Pro adds Office previews, media streaming, expiring preview shares and archive operations, with Viewer, Operator and Owner roles and audit export. Business adds questions answered from a single open document with a page citation, uploads, and restore from Glacier and Deep Archive.
Judge a browser-based S3 viewer on what it renders, how it is granted access, where contents travel, and what it records. A role-based connection and an honest list of limits matter more than the length of the feature list.