AWS · Amazon Web Services

What Is Amazon S3? Buckets, Storage Classes & Pricing (2026)

Last verified: June 17, 2026  ·  Format: Breakdown

Amazon S3 (Simple Storage Service) is Amazon's object storage service, built to store and retrieve any amount of data over the internet, and it is one of the best-known building blocks of the AWS cloud. If you have been asking what S3 is in practical terms, picture a near-limitless bucket where you drop files, images, backups, logs, datasets, and get them back by name from anywhere, with Amazon handling the hardware. It is designed for 99.999999999% (11 nines) of data durability and 99.99% availability by default, which is a large part of why teams trust it with data they cannot afford to lose.

This breakdown is plain and practical. We start with what S3 actually is, explain how buckets and objects work, walk through the storage classes from Standard to Glacier Deep Archive, show how S3 pricing is dimensioned, and close with when to reach for it. Service and pricing details below are drawn from AWS documentation and were checked on June 17, 2026; because pricing varies by region and changes often, always confirm current figures on the AWS site before you plan around them.

What Amazon S3 Is

S3 is object storage, which is a different model from the file systems and disks you may be used to. Instead of folders and drives, S3 stores each piece of data as an object: the data itself, plus metadata and a unique key (its name). You read and write objects through an API or the AWS console, and S3 takes care of where the bytes physically live, how they are replicated, and how they stay durable. The result is storage that scales to effectively any amount of data without you provisioning or managing capacity.

The headline guarantee is durability. S3 is designed for 99.999999999% (11 nines) of data durability, meaning that across a large set of objects the expected annual loss is vanishingly small, and it targets 99.99% availability for the Standard class by default. AWS achieves this by automatically storing copies of your data across multiple devices, and in most classes across multiple facilities, so a single hardware or facility failure does not lose your data.

Two ideas make S3 what it is. First, it is fully managed and elastic: you never run out of space, and you pay for what you store rather than buying disks ahead of demand. Second, it is the connective tissue of AWS, the default place to put files that other services read from and write to, from analytics to machine learning. If you want the broader context, our what is AWS guide places S3 alongside the other core services, and the Cloud Tools hub sets AWS next to the other providers.

Buckets and Objects

Everything in S3 lives in a bucket. A bucket is a container for objects: you create one, give it a globally unique name, choose the AWS Region it lives in, and then store objects in it. Each object has a key (its name), the data, and metadata, and you address it by bucket plus key. There are no drives to format and no volumes to grow; you simply put objects in and get them out, and the bucket scales with you.

S3 now offers more than one kind of bucket, because different workloads want different behavior. The main types are:

• General purpose buckets, the original and most widely used type, suitable for the vast majority of storage needs across all storage classes.
• Directory buckets, used with S3 Express One Zone for very low, consistent latency by keeping data in a single Availability Zone.
• Table buckets, purpose-built for storing tabular data for analytics workloads.
• Vector buckets, designed to store vector data for AI and machine-learning use cases such as similarity search.

For most people getting started, a general purpose bucket is the right answer, and the other types are specializations you adopt when a concrete need appears. Where your bucket lives is a real decision, not a default: the Region sets latency for nearby users and can carry legal weight for regulated data, which our guide to cloud regions, zones, and data residency covers in depth.

Amazon S3 Storage Classes

The single most important lever for S3 cost is the storage class. Every object you store sits in a class, and the class determines the trade-off between price, access speed, retrieval cost, and how long you are expected to keep the object. The idea is simple: data you touch constantly belongs in a fast, always-ready class, while data you rarely or never read belongs in a cheaper, archival class. Picking the right class, and letting S3 move objects between them automatically, is how teams keep storage bills under control.

Active and automatic tiers

S3 Standard is the default for frequently accessed, active data: highest performance, no minimum storage duration, no retrieval fee. S3 Intelligent-Tiering is the hands-off option: it automatically moves objects between access tiers based on usage, with no retrieval charge for moving data between its tiers, which makes it a strong default when access patterns are unpredictable. It auto-tiers objects of at least 128 KB.

Infrequent-access tiers

S3 Standard-IA (Infrequent Access) is for data you access less often but must retrieve quickly when you do; it carries a 128 KB minimum billable object size and a 30-day minimum storage duration, and it charges a per-gigabyte retrieval fee. S3 One Zone-IA is the same idea at lower cost, with the trade-off that it stores data in a single Availability Zone rather than spreading it across several, so it suits re-creatable data; it shares the 128 KB minimum and 30-day minimum duration. S3 Express One Zone is a high-performance, single-Availability-Zone class for latency-sensitive workloads, delivering single-digit-millisecond access and up to 10 times faster performance than S3 Standard.

Archive tiers

The Glacier classes are for data you keep for the long term and rarely read. S3 Glacier Instant Retrieval gives archival pricing with millisecond access for data you touch perhaps once a quarter; it has a 128 KB minimum and a 90-day minimum duration. S3 Glacier Flexible Retrieval lowers cost further for backups and disaster recovery, with a 90-day minimum duration and free bulk retrievals. S3 Glacier Deep Archive is the lowest-cost class, built for long-term retention you may access once or twice a year, with a 180-day minimum storage duration.

The pattern is consistent: the cheaper the class per gigabyte, the longer you are expected to keep the object and, for the archive tiers, the more you may pay to retrieve it. If you are unsure, S3 Intelligent-Tiering moves objects for you and removes the guesswork. Confirm the current per-class pricing and minimums for your Region on the official pricing page before you design a lifecycle policy around them.

How Amazon S3 Pricing Works

Understanding what S3 costs starts with how it is dimensioned, because there is no single price. You pay across several dimensions, and the total depends on how much you store, how often you read it, and where the data goes. Understanding the dimensions is how you keep an S3 bill predictable.

• Storage: charged per gigabyte stored, varying by storage class, the size of your objects, and how long you keep them. This is usually the biggest line item, and it is why the storage class you choose matters so much.
• Requests: charged per request for operations such as PUT, COPY, POST, LIST, GET, and lifecycle transitions. Notably, DELETE and CANCEL requests are free, so cleaning up does not cost you.
• Data retrievals: charged when you read data from the infrequent-access and archive classes, specifically Standard-IA, One Zone-IA, Glacier Instant Retrieval, and archive restores. The Standard and Intelligent-Tiering classes do not add a separate per-gigabyte retrieval charge.
• Data transfer: data transferred into S3 is free, and transfers within the same Region are free. Data transferred out to the internet is free for the first 100 GB per month, aggregated across AWS services and Regions (excluding China and GovCloud), and charged beyond that.

Because per-gigabyte rates differ from Region to Region and AWS adjusts them over time, treat any specific number as a starting point rather than a quote. The dependable way to estimate an S3 bill is to map your workload to these dimensions, pick storage classes deliberately, and confirm the current figures on the Amazon S3 pricing page for the Region you will actually use.

When to Use Amazon S3

We have covered what S3 is and how it is priced; the last question is when to reach for it. The short answer is whenever you need durable, scalable storage for data that is read and written as whole objects rather than edited in place. A few patterns dominate, and they map cleanly onto the storage classes above.

Honest Trade-offs

S3 is a sensible default, but it carries real trade-offs worth weighing. S3 is a sensible default for most storage needs, and the points below are not reasons to avoid it. They are reasons to adopt it with clear eyes.

Frequently Asked Questions