Storage service selection

5 minutes 5 Questions

Storage service selection is a critical component of workload migration and modernization on AWS, requiring architects to match application requirements with appropriate storage solutions. AWS offers diverse storage services categorized into block, file, and object storage types. Amazon S3 serves as the primary object storage solution, ideal for unstructured data, backups, archives, and static content. It provides eleven 9s of durability and integrates with various AWS services. S3 storage classes like Standard, Intelligent-Tiering, Glacier, and Glacier Deep Archive help optimize costs based on access patterns. Amazon EBS delivers persistent block storage for EC2 instances, supporting various volume types including gp3, io2, and st1 for different performance requirements. EBS is essential for databases, boot volumes, and applications requiring low-latency access to data. Amazon EFS provides scalable, elastic file storage for Linux workloads, enabling multiple EC2 instances to access shared data simultaneously. For Windows workloads, Amazon FSx for Windows File Server offers fully managed native Windows file systems with SMB protocol support. Amazon FSx for Lustre delivers high-performance file systems for compute-intensive workloads like machine learning and high-performance computing, integrating seamlessly with S3 for data processing. AWS Storage Gateway bridges on-premises environments with cloud storage, offering File Gateway, Volume Gateway, and Tape Gateway options for hybrid architectures during migration phases. When selecting storage services, architects must evaluate factors including performance requirements (IOPS, throughput, latency), durability and availability needs, access patterns, cost optimization opportunities, and integration requirements. Data classification, compliance requirements, and encryption needs also influence decisions. For migrations, AWS DataSync accelerates data transfer between on-premises storage and AWS, while AWS Transfer Family supports SFTP, FTPS, and FTP protocols for file transfers. Understanding these services enables architects to design resilient, cost-effective storage architectures that support both migration objectives and long-term operational efficiency.

Storage Service Selection for AWS Solutions Architect Professional

Why Storage Service Selection is Important

Storage service selection is a critical skill for AWS Solutions Architect Professional candidates because choosing the right storage solution directly impacts application performance, cost efficiency, data durability, and operational complexity. AWS offers numerous storage services, each optimized for specific use cases, and selecting the wrong service can lead to performance bottlenecks, excessive costs, or architectural limitations during migration and modernization efforts.

What is Storage Service Selection?

Storage service selection involves evaluating workload requirements and matching them with the most appropriate AWS storage service. The primary AWS storage services include:

Amazon S3 - Object storage for unstructured data, backups, archives, and static content
Amazon EBS - Block storage for EC2 instances requiring persistent, high-performance storage
Amazon EFS - Managed file storage for Linux workloads requiring shared access
Amazon FSx - Fully managed file systems (Windows File Server, Lustre, NetApp ONTAP, OpenZFS)
AWS Storage Gateway - Hybrid storage connecting on-premises environments to cloud storage
Amazon S3 Glacier - Low-cost archival storage for infrequently accessed data

How Storage Service Selection Works

The selection process involves analyzing several key factors:

1. Access Patterns
- Frequency of access (hot, warm, cold data)
- Read/write ratios
- Sequential vs random access

2. Performance Requirements
- IOPS requirements
- Throughput needs
- Latency sensitivity

3. Data Characteristics
- Structured vs unstructured data
- File sizes
- Total data volume

4. Sharing Requirements
- Single instance access (EBS)
- Multi-instance shared access (EFS, FSx)
- Global access (S3)

5. Protocol Requirements
- Block storage protocols
- NFS (EFS, FSx for Lustre)
- SMB (FSx for Windows)
- Object APIs (S3)

6. Cost Considerations
- Storage costs per GB
- Request costs
- Data transfer costs
- Lifecycle policies for cost optimization

Key Selection Guidelines

Choose Amazon S3 when: You need scalable object storage, static website hosting, data lakes, or backup destinations

Choose Amazon EBS when: You need high-performance block storage for databases or applications running on EC2

Choose Amazon EFS when: Multiple Linux instances need shared file system access with automatic scaling

Choose FSx for Windows File Server when: Windows applications require SMB protocol, Active Directory integration, or NTFS

Choose FSx for Lustre when: High-performance computing, machine learning, or media processing workloads need fast parallel file systems

Choose FSx for NetApp ONTAP when: Migrating NetApp workloads or needing multi-protocol access (NFS, SMB, iSCSI)

Choose Storage Gateway when: Hybrid scenarios require on-premises applications to access cloud storage seamlessly

Exam Tips: Answering Questions on Storage Service Selection

1. Identify the Protocol First
Questions often hint at the required protocol. SMB means FSx for Windows, NFS could mean EFS or FSx, block storage means EBS.

2. Look for Shared Access Keywords
Terms like 'multiple instances,' 'shared file system,' or 'concurrent access' point toward EFS or FSx rather than EBS.

3. Consider Migration Context
When migrating existing workloads, match the source storage type. Windows file servers migrate to FSx for Windows, NetApp to FSx for ONTAP.

4. Evaluate Performance Clues
High IOPS requirements suggest EBS io2 or io2 Block Express. HPC workloads suggest FSx for Lustre.

5. Watch for Cost Optimization Scenarios
Questions mentioning infrequent access or archival needs point to S3 Glacier or S3 Intelligent-Tiering.

6. Hybrid Scenarios Signal Storage Gateway
On-premises applications needing cloud storage integration typically require Storage Gateway solutions.

7. Eliminate Based on Constraints
EBS is limited to single Availability Zone attachment (except Multi-Attach for specific use cases). EFS spans multiple AZs.

8. Remember Service Limits
Know maximum file sizes, volume sizes, and throughput limits for each service to eliminate inappropriate options.

9. Data Lake Questions
Data lake scenarios almost always involve S3 as the foundation due to its scalability and integration with analytics services.

10. Read the Full Question
Pay attention to all requirements before selecting an answer. A solution might meet performance needs but fail on protocol or sharing requirements.
Test mode:
More Storage service selection questions
30 questions (total)

Other Accelerate Workload Migration and Modernization concepts

7Rs migration strategiesAmazon Aurora ServerlessAmazon DynamoDBAmazon EBSAmazon EC2 for migrationsAmazon ECRAmazon ECSAmazon EFSAmazon EKSAmazon ElastiCacheAmazon EventBridgeAmazon FSxAmazon OpenSearch ServiceAmazon RDSAmazon S3 storageAmazon S3 Transfer AccelerationApplication decoupling opportunitiesApplication integration service selectionApplication migration assessmentApplication transfer mechanism selectionAsset planning for migrationAWS Application Discovery ServiceAWS Application Migration ServiceAWS Database Migration Service (DMS)AWS DataSyncAWS Directory ServiceAWS Elastic BeanstalkAWS FargateAWS IAM Identity Center for migrationAWS LambdaAWS Migration HubAWS Schema Conversion Tool (SCT)AWS Snow FamilyAWS Storage GatewayAWS Transfer FamilyCompute platform selectionContainer hosting platform selectionContainer service selectionContainers for modernizationDatabase platform selectionDatabase transfer mechanism selectionData transfer service selectionDirect Connect for migrationEvent-driven architecture modernizationGovernance model selectionGovernance tools for migrationMicroservices modernizationMigration assessment toolsPortfolio assessmentPurpose-built database opportunitiesRefactor migration strategyRehost migration strategyRelocate migration strategyReplatform migration strategyRepurchase migration strategyRetain migration strategyRetire migration strategyRoute 53 for migrationSecurity methods for migration toolsSelf-managed databases on EC2Serverless compute offeringsServerless solution opportunitiesSite-to-Site VPN for migrationTotal cost of ownership (TCO) evaluationWave planning for migrationWorkload prioritization