Amazon S3

What This Service Solves

S3 stores objects in buckets. It is not a block device, file system, or relational database.

• Store durable objects, static assets, backups, logs, data lakes, and event sources.
• Use versioning, lifecycle, replication, object lock, and storage classes to match durability and cost needs.

When You Should Not Use It

• Do not use S3 when an application needs block-level writes, POSIX file semantics, or low-latency relational queries.

What AWS Manages and What You Manage

AWS manages storage fleet durability and availability. You manage bucket names, policies, object organization, encryption choices, lifecycle, replication, public access, and data classification.

Security Implications

Block Public Access, IAM policies, bucket policies, access points, KMS encryption, presigned URLs, and CloudTrail data events matter.

Availability and Scaling

S3 is regional. Cross-Region replication is a design choice, not automatic for every bucket.

S3 scales object access massively. Key design still matters for lifecycle, listing, event processing, and data-lake partitioning.

Cost Behavior

Cost depends on storage class, requests, retrieval, lifecycle transitions, replication, and data transfer.

Common Integrations

• CloudFront
• Lambda notifications
• EventBridge
• Athena
• Glue
• Backup
• Macie

How AWS Might Present It

Certification-Specific Depth

Related Comparisons

Sources and Review Metadata

This independent training application is not affiliated with or endorsed by Amazon Web Services. AWS, Amazon Web Services, and AWS certification names are trademarks of Amazon.com, Inc. or its affiliates.