Study guide

3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance

AWS Solutions Architect Associate SAA-C03

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the AWS Solutions Architect Associate (SAA-C03) Exam Study Strategies and Exam Tips for SAA-C03 The AWS Well-Architected Framework

2 Domain 1: Design Secure Architectures (30%)

1.1 IAM Fundamentals — Users, Groups, Roles, and Policies 1.2 AWS Organizations, SCPs, and Multi-Account Strategy 1.3 VPC Security — Security Groups, NACLs, and VPC Endpoints 1.4 Encryption, KMS, and Secrets Management 1.5 AWS WAF, Shield, and Network Firewall 1.6 GuardDuty, Inspector, Macie, and Security Hub 1.7 The Shared Responsibility Model for Solutions Architects 1.8 Data Protection, Compliance, and Audit Services

3 Domain 2: Design Resilient Architectures (26%)

2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB 2.2 EC2 Auto Scaling — Dynamic, Predictive, and Scheduled 2.3 Multi-AZ and Multi-Region Architectures 2.4 Disaster Recovery Strategies — RTO and RPO 2.5 Decoupling with SQS, SNS, and EventBridge 2.6 AWS Step Functions and Workflow Orchestration

4 Domain 3: Design High-Performing Architectures (24%)

3.1 EC2 Instance Types, Purchasing Options, and Placement Groups 3.2 Lambda, Serverless Compute, and Container Services 3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance 3.4 Block and File Storage - EBS, EFS, and FSx 3.5 Database Services - RDS, Aurora, DynamoDB, and More 3.6 CloudFront, Route 53, and Global Accelerator 3.7 Data Ingestion and Transformation - Kinesis, Glue, and EMR

5 Domain 4: Design Cost-Optimized Architectures (20%)

4.1 Compute Cost Optimization — Right-Sizing, RIs, Savings Plans, and Spot 4.2 Storage Cost Optimization — S3 Tiers, EBS, and Data Transfer 4.3 Database Cost Optimization 4.4 AWS Cost Management and Monitoring Tools

6 VPC and Networking Deep Dive

5.1 VPC Architecture — Subnets, Route Tables, and Gateways 5.2 VPC Connectivity — Peering, Transit Gateway, and Direct Connect 5.3 Amazon API Gateway 5.4 CloudFormation and Infrastructure as Code 5.5 AWS PrivateLink and Endpoint Services

7 Migration, Transfer, and Hybrid Services

6.1 The 7 Rs of Cloud Migration 6.2 AWS Snow Family — Snowball Edge Devices 6.3 CloudWatch, CloudTrail, and AWS Config 6.4 Amazon Cognito and Identity Federation 6.5 AWS DataSync and Transfer Family

8 Serverless Architecture and Application Services

7.1 Serverless Architecture Patterns 7.2 Advanced SQS Patterns — DLQ, Backpressure, and FIFO 7.3 Analytics Services — Athena, OpenSearch, and QuickSight 7.4 Container Orchestration — ECS, EKS, and ECR

9 Advanced Topics and Exam Scenarios

8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account 8.2 Caching Strategies and ElastiCache Patterns 8.3 Hybrid Architecture — DNS, Storage, and Compute 8.4 SAA-C03 Scenario Practice — Putting It All Together

3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance

Key Takeaways Explain This Topic AI

S3 offers tiers from S3 Standard (highest cost, instant access) down to S3 Glacier Deep Archive (lowest cost; Standard restores typically finish within 12 hours, Bulk within 48 hours); all tiers share 99.999999999% (11 nines) durability.

S3 Intelligent-Tiering auto-moves objects between access tiers with no retrieval fees - the default answer when access patterns are unknown or shifting.

Lifecycle policies automate transitions and expirations; objects move only down the class hierarchy, and IA classes carry a 30-day minimum, Glacier 90 days, Deep Archive 180 days.

S3 scales to 3,500 PUT/POST/DELETE and 5,500 GET/HEAD requests per second per prefix; multipart upload is required above 5 GB and recommended above ~100 MB.

S3 Object Lock in Compliance mode makes objects undeletable for the retention period even by the root account - the WORM compliance answer.

Last updated: October 2026

Quick Answer: Frequent access -> S3 Standard. Unknown/changing pattern -> Intelligent-Tiering. Infrequent but instant -> Standard-IA (or Glacier Instant Retrieval for archive priced data). Cold archive -> Glacier Flexible (minutes-hours) or Deep Archive (Standard restores typically within 12 hours, Bulk within 48). Automate moves with lifecycle policies; enforce immutability with Object Lock Compliance.

S3 Storage Classes

  • Class Availability SLA design Min duration Retrieval Use case
  • S3 Standard 99.99% None None Hot, frequently accessed data
  • S3 Intelligent-Tiering 99.9% None None (small monitoring fee) Unknown/changing access
  • S3 Standard-IA 99.9% 30 days Per GB Infrequent but needs instant access
  • S3 One Zone-IA 99.5% (1 AZ) 30 days Per GB Re-creatable infrequent data
  • S3 Glacier Instant Retrieval 99.9% 90 days Per GB Archive needing millisecond reads
  • S3 Glacier Flexible Retrieval 99.99% 90 days Per GB Archive, minutes to 12 hours

S3 Glacier Deep Archive 99.99% 180 days Per GB 7-10 yr compliance; restores within 12 h (Standard) or 48 h (Bulk)

Every class is designed for 99.999999999% (11 nines) durability by storing data redundantly. The differentiators are availability, minimum storage duration (early-delete fees apply if you remove sooner), per-GB storage price, and retrieval speed/cost. One Zone-IA stores in a single AZ , so it is cheaper but loses the object if that AZ is destroyed - use only for data you can regenerate.

Intelligent-Tiering Access Tiers

  • Tier Trigger Savings vs Standard
  • Frequent Access Default Standard pricing
  • Infrequent Access No access 30 days ~40%
  • Archive Instant Access No access 90 days ~68%
  • Archive Access (opt-in) 90-730 days Glacier-tier pricing
  • Deep Archive Access (opt-in) 180-730 days Deep Archive pricing

On the Exam: "Access pattern is unpredictable" -> Intelligent-Tiering. "Accessed a few times a year but must come back immediately" -> Standard-IA or Glacier Instant Retrieval. "Regulatory archive, retrieval can wait hours" -> Glacier Deep Archive.

S3 Lifecycle Policies

Lifecycle rules transition or expire objects automatically based on age. Objects move only down the hierarchy: Standard -> Standard-IA / One Zone-IA -> Glacier Instant -> Glacier Flexible -> Glacier Deep Archive -> Expire

  • Day Action
  • 0 Created in S3 Standard
  • 30 Transition to Standard-IA
  • 90 Transition to Glacier Flexible Retrieval
  • 365 Transition to Glacier Deep Archive
  • 2555 (7 yr) Expire (delete)

Lifecycle rules can also expire old noncurrent versions in versioned buckets and clean up incomplete multipart uploads.

S3 Performance

  • Metric Value
  • PUT/COPY/POST/DELETE 3,500 requests/sec per prefix
  • GET/HEAD 5,500 requests/sec per prefix
  • Object size 0 bytes to 5 TB
  • Multipart upload Required above 5 GB; recommended above ~100 MB

Scaling technique: request limits are per prefix, so spreading objects across many key prefixes (e.g. /2026/01/ , /2026/02/ ) multiplies throughput. Use multipart upload for parallel, resumable large uploads, byte-range fetches to parallelize downloads, and S3 Transfer Acceleration (routes through CloudFront edge locations) to speed long-distance uploads by 50-500%.

Versioning, Object Lock, and Access Points

Versioning keeps every object revision; a delete creates a recoverable delete marker, and MFA Delete can require a hardware token to permanently remove versions. S3 Object Lock enforces write-once-read-many (WORM):

  • Mode Behavior
  • Governance Privileged users can override the lock
  • Compliance Nobody, including the root account, can delete before retention expires
  • Legal Hold Indefinite lock until explicitly removed

S3 Access Points give each application its own hostname and scoped policy over a shared bucket, optionally pinned to a VPC, which simplifies otherwise enormous bucket policies for large shared datasets.

On the Exam: "Data must be immutable for 7 years, even from administrators" -> Object Lock in Compliance mode. "Speed up uploads from users in distant Regions" -> Transfer Acceleration.

Worked Scenario: Designing a Lifecycle

Imagine compliance logs that auditors read constantly for the first month, occasionally for the following year, and almost never afterward - yet the records must survive for seven years. The cost-optimal design transitions the objects through progressively cheaper classes that match each phase: leave new objects in S3 Standard while hot, transition to Standard-IA at day 30 once access drops, move to Glacier Deep Archive at day 365 for the long cold tail, and add an expiration action at day 2,555 (seven years) to delete them automatically.

Note the minimum-duration fees: an object moved out of Standard-IA before 30 days, or out of Deep Archive before 180 days, still incurs the minimum-duration charge, so do not transition data faster than its real access pattern justifies.

Common Traps to Avoid

One Zone-IA for irreplaceable data. One Zone-IA stores in a single AZ; if that AZ is lost, the data is gone. Use it only for data you can regenerate.

Versioning is not immutability. Versioning protects against accidental overwrite but a privileged user can still purge versions. For true WORM compliance you need Object Lock in Compliance mode.

Transfer Acceleration for downloads. Transfer Acceleration speeds long-distance uploads via edge locations; to accelerate downloads to end users, put CloudFront in front of the bucket.

Per-prefix throughput. S3 scales to 5,500 GET and 3,500 PUT requests per second per prefix - concentrating a hot workload on one prefix triggers 503 Slow Down errors; spread keys across prefixes.

Intelligent-Tiering monitoring fee. Intelligent-Tiering charges a small per-object monitoring fee; for tiny objects or a known, predictable access pattern, explicit lifecycle transitions can be cheaper.