aws ebs vs aws efs vs aws s3
Amazon EFS is a file storage service for use with Amazon compute (EC2, containers, serverless) and on-premises servers. EFS provides a file system interface, file system access semantics (such as strong consistency and file locking), and concurrently accessible storage for up to thousands of EC2 instances.
Amazon Elastic Block Store (EBS) is a block-level storage service for use with EC2. Amazon EBS can deliver performance for workloads that require the lowest-latency access to data from a single EC2 instance.
Amazon Simple Storage Service (S3) is an object storage service. Amazon S3 makes data available through an internet API that can be accessed anywhere.
efs vs s3
Amazon EFS provides shared access to data using a traditional file sharing permissions model and hierarchical directory structure via the NFSv4 protocol. Applications that access data using a standard file system interface provided through the operating system can use Amazon EFS to take advantage of the scalability and reliability of file storage in the cloud without writing any new code or adjusting applications.
Amazon S3 is an object storage platform that uses a simple API for storing and accessing data. Applications that do not require a file system structure and are designed to work with object storage can use Amazon S3 as a massively scalable, durable, low-cost object storage solution.
efs vs ebs
Amazon EFS provides shared file storage for use with compute instances in the AWS Cloud and on-premises servers. Applications that require shared file access can use Amazon EFS for reliable file storage delivering high aggregate throughput to thousands of clients simultaneously.
Amazon EBS is a cloud block storage service that provides direct access from a single Amazon EC2 instance to a dedicated storage volume. Applications that require persistent dedicated block access for a single host can use Amazon EBS as a highly available, low-latency block storage solution.
Comparision of aws efs vs aws s3 vs aws ebs
|Performance||Per-operation latency||Low, consistent||Low, for mixed request types, and integration with CloudFront||Lowest, consistent|
|Throughput scale||Multiple GBs per second||Multiple GBs per second||Single GB per second|
|Characteristics||Data Availability/Durability||Stored redundantly across multiple AZs||Stored redundantly across multiple AZs||Stored redundantly in a single AZ|
|Access||One to thousands of EC2 instances or on-premises servers, from multiple AZs, concurrently||One to millions of connections over the web||Single EC2 instance in a single AZ|
|Use Cases||Web serving and content management, enterprise applications, media and entertainment, home directories, database backups, developer tools, container storage, big data analytics||Web serving and content management, media and entertainment, backups, big data analytics, data lake||Boot volumes, transactional and NoSQL databases, data warehousing & ETL|