Object Storage (OSS)
Secure, elastic storage at scale
Store and distribute data at any scale, S3-compatible with three-replica durability. Ideal for static assets, backups, data lakes, and analytics — pay only for what you use.
Core capabilities
S3-compatible and portable
Three-replica durability (11 nines)
Lifecycle policies to cut cost
CDN direct-accelerated delivery
What object storage is for
Images, video, backups, log archives, raw data-lake files, static site assets — anything written once, read many times, and accessed as whole objects belongs in object storage.
Conversely, workloads needing frequent random rewrites, file locks, or POSIX semantics — database files, shared filesystems — do not belong here. That is what block and file storage are for.
A bucket bill has three parts
Capacity, request count, and egress. Capacity is the visible one, but the other two are what run away: many small objects read frequently drive request charges up fast, and serving downloads straight from a bucket makes egress your single most expensive line.
The standard fix is to put a CDN in front. Cache hits bill at CDN rates; only cache misses bill as object-storage egress. That one change often removes a large share of delivery cost.
Lifecycle rules are the easiest win
Attach a lifecycle policy: move to infrequent-access after N days, to archive after N more, delete after that. Tiering hot and cold data lands the same volume on far lower unit prices, with no application changes at all.
Pairs well with
Cross-border E-commerce
View detailsGlobal Gaming Infrastructure
View detailsFintech Solutions
View detailsFrequently asked questions
Object storage or block storage — which one?
It comes down to access pattern. Object storage is reached over HTTP(S) as whole objects: ideal for static assets, backups, and archives, effectively unlimited, and cheap per GB. Block storage mounts as a device: random I/O, can host a database, but capped in size and priced higher. Most architectures use both.
Can data be lost in object storage?
Mainstream object storage keeps multiple replicas or erasure-coded shards, with published durability around eleven nines — meaning a lost object is theoretically a once-in-millions-of-years event. The realistic risk is accidental deletion, which versioning and cross-region replication address directly.
How do I keep a public bucket from being scraped?
Keep the bucket private and allow only authorized accounts or CDN origin pulls. Expose public assets through a CDN domain with hotlink protection, a Referer allowlist, and per-IP rate limits — so even a leaked URL cannot push egress straight onto your bucket.
Related reading
AWS Shield Advanced: what is free, what is billed
Shield Advanced covering your WAF costs is true, with four boundaries: only protected resources, only standard features, and subject to a request ceiling. Bot Control, CAPTCHA and web ACLs above 1,500 WCUs are still billed separately.
Cloud CostAWS private pricing (EDP): threshold, risk, shortcut
Private pricing is the highest-threshold layer of the AWS discount system: a cross-service discount rather than a single-service commitment. Two traps come first - a shortfall payment if you miss the commitment, and mandatory enterprise support. And AWS states plainly that buying through a partner qualifies too.
Cloud CostMulti-cloud cost visibility: unify categories first
Each provider runs its own billing system, so there is no ready-made unified view. Most people reach for a tool first, which reverses the order: unify the cost categories and the tagging scheme first. Four accounting mismatches will make the numbers disagree.