Files your app or website serves
Product images, signed PDFs, user uploads. Put CloudFront in front and the bucket itself never has to be public.
Amazon S3 · AWS Partner · Los Angeles
Hot files close at hand, old ones on the cheap stairs, nothing public by accident.
Amazon S3 is AWS’s object storage: you put files of any kind in “buckets” and pay each month for the gigabytes you keep, the requests you make and the data you send out. We design those buckets for US companies, move files in from servers and other clouds, lock down who can read them, and write lifecycle rules so last year’s files stop costing this year’s prices. Then we hook S3 up to Zoho, so documents and backups land where your team already works.
01Where Amazon S3 fits
S3 stores whole files as objects, each with a key and some metadata, and serves them over HTTPS. AWS designs it for 99.999999999% durability, and most storage classes keep copies across at least three Availability Zones. That makes it brilliant for files you write once and read many times, and an awkward fit for anything that edits bytes in place.
Product images, signed PDFs, user uploads. Put CloudFront in front and the bucket itself never has to be public.
Database dumps, exports from business apps, seven years of tax records. Versioning and Object Lock stop deletes, accidental or not.
CSV, JSON and Parquet files that Athena can query where they sit, without loading a database first.
A file lands, S3 sends an event, and Lambda resizes, scans or forwards it. No server waits around polling a folder.
Office staff want folders, previews and co-editing. That’s a job for Zoho WorkDrive or Amazon FSx, with S3 behind it for archives.
Rows that change every second belong in RDS or DynamoDB, and an operating system needs an EBS volume. Rewriting one small object over and over gets slow and pricey.
02Amazon S3 services
Most S3 projects we pick up are one of five jobs. Some start from an empty AWS account; plenty start from a bucket that grew for six years with nobody owning it.
Which buckets, which prefixes, which Region, who owns each one, and how tags feed cost reports. Decided once, written down.
From a Windows file server, a NAS, Azure Blob or Google Cloud Storage, usually with AWS DataSync. Checksums verified, folder structure kept.
Block Public Access at the account level, bucket policies scoped to roles, SSE-KMS where keys matter, and IAM Access Analyzer to catch outside sharing.
S3 Storage Lens to see where the gigabytes really sit, then lifecycle rules, Intelligent-Tiering and cleanup of stale multipart uploads.
Versioning on the buckets that matter, replication to a second Region if the business needs it, and a restore drill so the backup is proven.
03S3 lifecycle rules, step by step
A lifecycle rule tells S3 to move objects to a cheaper class as they age, then delete them when you no longer have to keep them. Follow one sample invoice down the stairs. Every step lowers the monthly price per gigabyte and raises what it costs, in money or waiting time, to read it back.
Day 0
Finance opens it a few times in the first weeks. Reads cost only the request; no retrieval fee.
Day 30
Still opens in milliseconds, just with a $0.01 per GB retrieval fee. S3 won’t move objects here before day 30.
Day 90
Audit season might need it, and it still opens instantly. Reads cost $0.03 per GB, and it bills at least 90 days.
Day 180
Now a restore job comes first: minutes with expedited, 3 to 5 hours standard, free bulk restores in 5 to 12 hours.
Day 365
The cheapest shelf AWS sells. Standard restores finish within 12 hours, bulk within 48. Minimum stay: 180 days.
Year 7
Retention period met, so the rule removes it. With Object Lock on, nobody could delete it earlier.
04Try it · sample estimate
Tell it how much you store, how much of it gets read back each month and how fast you need it. It prices every class with AWS’s US East (N. Virginia) list rates for storage and retrieval, greys out the ones that can’t meet your needs, and picks one. Treat the result as a sample: request fees and data transfer sit on top.
Sample estimate using AWS list prices for US East (N. Virginia): storage per GB-month, retrieval per GB read (standard restores for Glacier Flexible Retrieval, bulk restores for Deep Archive). Intelligent-Tiering assumes objects averaging 1 MB, a $0.0025 monitoring fee per 1,000 objects, the read share staying in its frequent tier and the rest split between its infrequent and archive instant tiers. Minimum storage durations and the 128 KB minimum object charge are not modeled.
05Amazon S3 + Zoho
Zoho holds the customer, the deal and the invoice. S3 is a better home for the heavy files around them and for long-term copies of the data itself. These are the patterns we build most, each a short chain of AWS pieces we monitor.
Large files on a CRM record
Drawings, videos and site photos skip CRM’s own storage. The record keeps a link that only works for signed-in users. See our Zoho CRM work.
Nightly copy of Zoho data
Your CRM, Books and Inventory records exported on your schedule into a bucket you own, then walked down to Deep Archive by a lifecycle rule.
Upload in, record updated
A signed form or ID document arrives through your portal, and the matching contact or deal moves to the next stage on its own. Zoho Flow handles the no-code half.
Files as a reporting source
Usage files from your product or a vendor drop into a bucket, and dashboards in Zoho Analytics refresh from them on a schedule.
06Amazon S3 pricing
Five meters make up an S3 bill: gigabytes stored per month (by storage class), requests, retrieval fees on the colder classes, data sent out to the internet, and optional features like replication, Storage Lens advanced metrics or Inventory. Uploading data into S3 from the internet is free. Here are AWS’s list rates for US East (N. Virginia).
| Storage class | Storage, per GB-month | Retrieval, per GB | First byte | Minimum stay |
|---|---|---|---|---|
| S3 Standard | $0.023first 50 TB · $0.022 next 450 TB · $0.021 above | None | Milliseconds | None |
| S3 Intelligent-Tiering | $0.023 / $0.0125 / $0.004frequent / infrequent / archive instant tiers, plus $0.0025 per 1,000 monitored objects | None | Milliseconds | None |
| S3 Standard-IA | $0.0125 | $0.01 | Milliseconds | 30 days |
| S3 One Zone-IA | $0.01one Availability Zone only | $0.01 | Milliseconds | 30 days |
| S3 Glacier Instant Retrieval | $0.004 | $0.03 | Milliseconds | 90 days |
| S3 Glacier Flexible Retrieval | $0.0036 | $0.01 standard · bulk $0 | Minutes to 12 hours | 90 days |
| S3 Glacier Deep Archive | $0.00099 | $0.02 standard · $0.0025 bulk | Within 12 to 48 hours | 180 days |
AWS list prices in USD before tax, US East (N. Virginia); Oregon and other US Regions differ a little, and AWS revises rates now and then, so we recheck your Region’s figures when we model a bucket. Our side of an S3 project, from bucket design to lifecycle rules and Zoho links, is one fixed price written into a signed BRD, never a share of what you pay AWS.
07Amazon S3 questions
Storage classes, Glacier restore times, public buckets and how S3 compares with the drives your team already uses. Have a Storage Lens report or a recent S3 line from your bill? Bring it to the first call; that call is on us.
Amazon S3 (Simple Storage Service) is AWS object storage. Businesses use it for files their apps and websites serve, user uploads, backups and long-term archives, logs, and data that tools like Athena query in place. It is a poor fit for a shared drive people edit all day, a database, or a server's operating system disk.
In US East (N. Virginia), S3 Standard lists at $0.023 per GB-month for the first 50 TB, so 1 TB costs about $23.55 a month to store. Colder classes are cheaper to store: Standard-IA $0.0125, Glacier Instant Retrieval $0.004, Glacier Flexible Retrieval $0.0036 and Glacier Deep Archive $0.00099 per GB-month, but they add retrieval fees and minimum storage periods. Requests and data sent to the internet are billed on top.
Use S3 Standard for files read often. Standard-IA suits files read a few times a year that still need to open in milliseconds, as long as each object stays at least 30 days. Glacier Instant Retrieval is cheaper for data read about once a quarter. Glacier Flexible Retrieval and Deep Archive are for archives where waiting minutes, hours or up to two days for a restore is fine.
Often, when you cannot predict access. It moves each object between frequent, infrequent and archive instant tiers based on use, with no retrieval fees, for a monitoring fee of $0.0025 per 1,000 objects a month in US East. Objects smaller than 128 KB are not monitored and always stay in the frequent tier, so for millions of tiny files the math can favor a plain lifecycle rule.
No. Since April 2023, new buckets have S3 Block Public Access turned on and access control lists disabled by default, and since January 2023 S3 encrypts every new object at rest by default. Older buckets may predate those defaults, which is why we check each bucket's settings and policies on any account we take over.
Standard restores from Glacier Deep Archive finish within 12 hours and bulk restores within 48 hours. Glacier Flexible Retrieval is faster: expedited in minutes, standard in 3 to 5 hours, bulk in 5 to 12 hours. Glacier Instant Retrieval needs no restore at all and opens in milliseconds.
Google Drive, Dropbox and Zoho WorkDrive are file-sharing tools for people, with folders, previews, comments and co-editing. Amazon S3 is storage for applications and archives, accessed through APIs, with fine-grained permissions, lifecycle rules and very low archive prices. Many companies use both: Zoho WorkDrive for the team and S3 for app files, backups and records that must be kept for years.
Yes, with a small integration. We build a button or widget in Zoho CRM that gets a signed upload link from AWS Lambda, so large files go straight to your bucket and the record keeps the link. For backups, a scheduled Lambda exports your Zoho CRM, Books or Inventory data through Zoho's APIs into a versioned bucket you own.
AWS designs S3 for 99.999999999% (eleven nines) durability of objects over a year. Most storage classes keep data across at least three Availability Zones in a Region. One Zone-IA keeps it in a single zone, so it suits data you could recreate. For protection against deletes, add versioning, Object Lock or replication to a second Region.
The first call costs nothing. After that, each S3 project, whether a migration, a lifecycle and security cleanup or a Zoho integration, gets a fixed price written into a signed BRD with a delivery schedule. Large file server exits may need a paid assessment first, quoted up front. AWS bills you directly for storage and requests.
08Starting an S3 project
A one-bucket cleanup can usually be scoped from the first conversation. A file server exit with terabytes to move, or retention rules a regulator cares about, may need a paid assessment and BRD phase first; we’ll quote that before it starts.
Curious what happens after the BRD is signed for a storage project? See how we work →
09Let’s talk
Book a free consultation with Elite Tech Global. We review your Zoho, AWS, Shopify or WordPress setup, show where AI / SI agents can save time, and agree the next step. If we work together, every requirement and a fixed price go into a signed BRD before the build starts.
Real people, one team. Led by co-founders Ikramul Karim and Khris Kakosimidi, and a 40+ member team across Zoho, AWS and AI.
Thanks, we’ve got it.
We’ll review your request and email you to set up your free consultation. Prefer to pick a time now?
Book a call