Key points

• S3 stores objects in buckets and is accessed through service APIs; it is not attached block or ordinary POSIX file storage.
• Storage class and lifecycle decisions depend on access frequency, retrieval time, resilience, retention, and request/retrieval costs.
• Versioning, replication, Object Lock, encryption, access points/policies, and backups solve distinct protection and access needs.

Best-known use cases

• Store data lakes, static assets, logs, backups, and durable application objects.
• Serve as an origin for CloudFront or a destination for streaming/transfer pipelines.

What candidates often confuse it with

• S3 is object storage; EBS is block and EFS/FSx are file storage.
• S3 replication supplies copies; lifecycle changes storage class; neither is automatically an independent backup.

Key takeaway

Choose S3 for durable object storage, then design access, class, lifecycle, protection, and delivery separately.

Related services

• Amazon CloudFront
• AWS Backup
• AWS DataSync
• Amazon S3 Glacier

Relevant exam tasks

• D1.3
• D2.1
• D2.2
• D3.1
• D3.5
• D4.1

Learn more

• Amazon S3