Chapter 6 of 6 · 2 min
How do I give a non-technical person access to an S3 bucket?
SHORT ANSWER
Four ways, from most painful to least: an Amazon login, a desktop app, an internal page your developers build, or a hosted workspace they sign in to with their email.
The lesson 4 film is on chapter 1.
The four ways
- An IAM user, an Amazon login with permission for one bucket. They land in the console and inherit its vocabulary.
- A desktop app such as S3 Browser or Cyberduck, which gives them a folder window with access keys, Amazon keys, stored on their machine.
- An internal web page built on Storage Browser for S3, a folder view component Amazon publishes. Familiar, but your developers build, host and maintain it.
- A hosted file workspace. An administrator connects the bucket once, then invites people by email. Nobody receives Amazon keys.
What the last one costs
- $0
- BucketDesk Minimum: one bucket, PDF, image and text previews, for a small team
- $1,000a year
- Standard: every bucket, Office previews, sharing with people outside the company, team roles
Who can see what is set per person in the workspace, in plain language, instead of in Amazon permission policies.
Prices are for US East, October 2026. S3 access for non-technical teams: the complete guide has every rate and the steps.
NEXT · LESSON 5 BEGINSHow do I send a file to someone with no AWS account?A link that works for a week, and three things it cannot do.The same bucket, two ways
Compare with the AWS Console See the steps to open, share and give a colleague access in the AWS Console and in BucketDesk, side by side.