Storage access patterns

Task Statement 4.1: Design cost-optimized storage solutions.

📘AWS Certified Solutions Architect – (SAA-C03)


Explained

When designing cost-optimized storage solutions, understanding how your data is accessed is crucial. AWS storage pricing and performance options depend heavily on how often and how quickly you need to access data. This is what we call storage access patterns.

1. What are Storage Access Patterns?

A storage access pattern describes how data is used or retrieved from storage. This includes:

  • Frequency of access – How often the data is read or written.
  • Latency requirements – How quickly the data needs to be available.
  • Throughput requirements – How much data needs to be processed per second.

AWS uses these patterns to help you choose the most cost-efficient storage solution.


2. Common Storage Access Patterns in AWS

AWS categorizes access patterns mainly into four types:

a) Frequent Access

  • Description: Data is accessed often. You need low latency and high performance.
  • AWS Storage Options:
    • Amazon S3 Standard – Best for frequently accessed objects like active configuration files, application logs, or media files used regularly.
    • Amazon EBS General Purpose SSD (gp3/gp2) – Best for OS volumes, databases, or workloads requiring fast read/write performance.
  • Cost Implication: Higher storage cost but justified by fast access.

Exam Tip: If you see “frequently accessed data” in a question, look for S3 Standard or EBS SSD options.


b) Infrequent Access

  • Description: Data is accessed less often but still must be available quickly when needed.
  • AWS Storage Options:
    • Amazon S3 Standard-Infrequent Access (S3 Standard-IA) – Good for backups, old logs, or archives that you might need occasionally.
    • Amazon EBS Cold HDD (sc1) – Suitable for large volumes that are rarely used.
  • Cost Implication: Lower storage cost, but there may be a small retrieval cost when accessing the data.

Exam Tip: S3 Standard-IA is cheaper than S3 Standard, but accessing data incurs request costs.


c) Archive / Long-term Storage

  • Description: Data is rarely accessed, often for compliance or historical purposes.
  • AWS Storage Options:
    • Amazon S3 Glacier – Low-cost storage for long-term backups and logs. Retrieval takes minutes to hours.
    • Amazon S3 Glacier Deep Archive – Cheapest option, retrieval can take up to 12 hours.
  • Cost Implication: Very low storage cost. Access is slow and may have additional retrieval charges.

Exam Tip: When the question mentions “archival storage for compliance or infrequent access,” S3 Glacier or Deep Archive is the right choice.


d) Streaming / Big Data Access

  • Description: Data is accessed continuously or in high-volume streams. Common in analytics and log processing.
  • AWS Storage Options:
    • Amazon S3 + AWS Glue / Athena – For analytics queries over large datasets.
    • Amazon EFS (Elastic File System) – Provides scalable file storage for workloads requiring multiple EC2 instances accessing the same files.
  • Cost Implication: Pricing depends on storage size and throughput.

3. How AWS Pricing Relates to Access Patterns

Understanding access patterns is critical for cost optimization:

Access PatternRecommended AWS StorageCost Behavior
Frequent AccessS3 Standard, EBS SSDHigh storage cost, no retrieval cost
Infrequent AccessS3 Standard-IA, EBS Cold HDDLower storage cost, small retrieval cost
Archive / Long-term StorageS3 Glacier, S3 Glacier Deep ArchiveVery low storage cost, retrieval cost & latency
Streaming / Big DataS3 + Analytics, EFSCost depends on throughput and storage

Key Exam Point: AWS storage classes are optimized for specific access patterns, not just storage size. Picking the wrong class can increase costs unnecessarily.


4. Examples of Access Patterns in an IT Environment

  • Frequent Access: Web server logs that need to be accessed in real-time for monitoring.
  • Infrequent Access: Monthly backup snapshots of databases.
  • Archive: Compliance logs from three years ago stored in Glacier.
  • Streaming / Big Data: Sensor data ingested continuously into S3 for analytics with Athena.

These examples help you reason out which storage service fits best during exam scenarios.


5. Tips for the Exam

  1. Look for keywords in the question: “frequently accessed,” “rarely accessed,” “archival,” or “analytics.”
  2. Match the AWS storage class to the access pattern for both cost and performance.
  3. Remember retrieval costs and latency for IA and Glacier classes.
  4. Understand the difference between block, object, and file storage in the context of access patterns.

Summary:
Storage access patterns in AWS describe how your data is used, and knowing them helps you choose the right service to balance cost and performance. Frequent access needs speed (Standard or SSD), infrequent access needs cost efficiency (Standard-IA or sc1), and archival storage prioritizes ultra-low cost (Glacier / Deep Archive). Streaming or analytics workloads have special needs like EFS or S3 + query tools.

Buy Me a Coffee