One bucket, five laptops, zero chaos — if you set the rules before the first file lands. Per-person keys, versioning switched on, delete rights kept tight, and an exit that takes two minutes.
A mounted S3 drive works so well for one person that teams adopt it by instinct — usually by forwarding the same key to everyone. That shortcut poisons everything. This guide sets up team sharing properly: who gets which key, how overwrites are survived, and how a person leaves without taking the filing cabinet with them.
The team layout that survives real offices. Shared secrets and shared edits are where team buckets go wrong.
The single worst team habit is emailing one access key to everyone. It feels fast and it destroys accountability and security together: you cannot tell who deleted a file, and when someone leaves, you cannot remove their access without breaking everyone's drive. Create an IAM user per person, named after them. Five minutes each, once. This one rule is the difference between a team tool and a team incident.
On a team bucket, enable versioning in the S3 console before anyone mounts the drive. S3 then keeps the previous version every time a file is overwritten or deleted, and you can restore it. This matters because of the drive's biggest honest limit: there is no file locking. If two people open the same spreadsheet, both can save, and the last save silently wins. Versioning turns that disaster into a recoverable mistake.
Working rule to announce to the team on day one: if you are editing it, say so — in chat, in person, anywhere. Low-tech, completely effective.
report-2026-10-25.xlsx style names end most overwrite arguments before they startWhen someone leaves the team, the exit is as clean as the entry was: open their IAM user, deactivate and delete their access key, done. Their drive stops working, everyone else's keeps working, and nothing they uploaded is lost. Compare that with the shared-key office, where a departure means changing the key on every single PC. Also review the access logs for their key if the departure was not a friendly one, and check CloudTrail when you need to answer who-did-what questions — with per-person keys, that question actually has an answer.
Every click shown live — installing TntDrive, adding the S3 account and mapping the drive in Windows.
▶️ Watch Full VideoThey can open it, but S3 drive tools have no file locking, so both are editing private copies and the last save overwrites the other without any warning. Versioning lets you recover the overwritten version, and a simple announce-before-editing habit prevents most collisions in small teams.
Open their IAM user and deactivate, then delete, their access key. Their drive stops immediately, their uploaded files stay in the bucket, and nobody else's setup changes. This is only possible because every person had their own key from the start.
Enable CloudTrail or S3 access logging on the bucket — actions are recorded against the IAM user who performed them, which is another reason shared keys are useless: with one key for all, the log blames everyone and no one.