LEARN. PRACTICE. GROW.Concept and mechanism
Object, file, and block storage expose different interfaces. For files shared by Linux clients, EFS provides NFS; a Regional choice should be distinguished from One Zone. For Windows applications depending on SMB and Active Directory integration, assess FSx for Windows File Server. EBS provides block volumes associated with compute architecture, with capacity, IOPS, and throughput to size. With gp3 these dimensions can be assessed separately within supported limits; increasing capacity should not be the only response to latency.
Guided application
For a large S3 upload, multipart permits retrying failed parts without resending everything; also arrange handling of incomplete uploads. With CloudFront delivery, the cache key should represent dimensions changing the response, such as language. For S3 classes, compare access frequency and latency, minimum duration, and retrieval charges. Intelligent-Tiering can follow variable patterns, but eligibility, monitoring, and archive options require assessment. If EBS optimization needs less capacity, do not plan a direct shrink of the existing volume: prepare migration to another volume and validate data.
A rarely read report still needs immediate access. The lowest per-GB storage class may involve a retrieval wait incompatible with that requirement.
Common pitfalls
Treating S3 as a filesystem without adaptation; excluding language from cache; ignoring retrieval costs or incomplete uploads.
Related topics: Databases, replicas, and cache · Events, queues, and processing
Choose according to access semantics and total lifecycle cost.
Reference: Amazon EFS overview · SAA-C03