Objects, blocks, files, and networking | AWS Cloud Practitioner: foundational decisions

Understand the concept

S3 stores objects; EBS provides block volumes for compatible compute; EFS provides a shared filesystem. Interfaces are not interchangeable merely because all store bytes. Consider concurrent access, latency, protocols, durability, and retention. Less-frequent-access storage classes may have specific retrieval costs and timing.

Apply and decide

A VPC organizes logical networking; subnets, routes, and controls determine allowed paths. A private-network resource is not automatically free of other risks. Service and identity authorization still matter. Load balancing and caching address different web-traffic needs; a CDN reduces distance for eligible content but does not fix application logic.

Workplace application

A banking archive may be rarely queried and still need fast responses. Separate access frequency from acceptable retrieval time. Compare the storage interface with the application: objects, blocks, and files behave differently. For web content, distinguish CDN delivery from balancing among instances. During selection, record concrete requirements rather than automatically choosing the cheapest class or most familiar service.

IN PRACTICE

Reports read through an API and stored as objects fit S3. An application requiring a shared filesystem should evaluate EFS or another file option.

Common pitfalls

Choosing archives only by price or treating every Glacier class as identical.

Related topics: Costs, observability, and auditing · Cloud and shared responsibility

Take this idea with you

Interface and access pattern come before storage selection.

Create account

Reference: Choosing an AWS storage service · CLF-C02