Storage class, requests and downloads out — your S3 bill has three moving parts, and the drive changes how all three behave. This guide explains each line honestly, without pinning prices that change by region and date.
People mount an S3 drive expecting one simple cost — rent for space — and then get surprised by a bill with more lines on it. Nothing here is a trick; it is simply how S3 pricing works when a drive tool starts generating requests like a busy office worker. Prices themselves vary by region and change over time, so this guide teaches you the shape of the bill, which never changes.
The shape of an S3 bill. Amounts depend on region and storage class — check the official AWS pricing page for current figures.
You pay for the space your files occupy, billed by the gigabyte per month, at the rate of the storage class you chose. Standard storage is the everyday class. The cheaper archive classes (the Glacier family) cut storage cost hard but make retrieval slower and separately charged — fine for backups you hope never to open, wrong for a working drive you browse daily. Mounted drives should live on standard storage.
S3 also charges for operations: listing a folder, reading a file, saving a file, deleting a file. Each one costs a tiny fraction, but a mounted drive generates them constantly — every Explorer refresh lists, every thumbnail reads, every save writes. A drive used gently costs almost nothing in requests. A drive browsed aggressively all day, or pointed at by software that polls folders, adds up. This is the real reason a tiny bucket can still produce a visible bill.
Moving data into S3 over the internet is free. Moving data out to the internet is charged per GB. For a personal drive used normally this stays modest. It stops being modest if the mounted bucket becomes a public download source or the team downloads the same huge files again and again — the cache helps here, because a cached file is not re-downloaded on every open.
If you switch on bucket versioning (recommended for team buckets, see the team guide in this series), every edit keeps the old version too — safer, and slightly more storage. The bigger silent cost is simpler: buckets collect forgotten test files, duplicate backups and abandoned uploads forever, and S3 bills faithfully for all of it. Review the bucket a few times a year and delete what nobody needs. S3 charges you for what you keep, not for what you remember keeping.
Every click shown live — installing TntDrive, adding the S3 account and mapping the drive in Windows.
▶️ Watch Full VideoAWS gives new accounts a free tier that includes a limited amount of S3 storage and requests for the first 12 months. It is a tasting portion, not a plan — a mounted drive used daily can pass the free request limits quickly, so watch the billing dashboard from the first month itself.
Almost always requests or downloads. A small bucket browsed constantly still generates thousands of billable list and read operations, and downloads out to the internet are charged by the GB. Open AWS Cost Explorer and look at which of the three lines — storage, requests, transfer — actually grew.
Use the S3 drive on standard storage for files you open regularly, and lifecycle rules or manual moves to push old backups into an archive class like the Glacier family. Storage gets much cheaper there, in exchange for slow, separately charged retrieval — a fair trade for files you may never open.