AWS EFS vs EBS vs S3 (differences & when to use?)
As per the title of this question, what are the practical differences between AWS EFS, EBS and S3?
My understanding of each:
- S3 is a storage facility accessible any where
- EBS is a device you can mount onto EC2
- EFS is a file system you can mount onto EC2
So why would I use EBS over EFS? Seem like they have the same use cases but minor semantic differences? Although EFS is replicated across AZs where as EBS is just a mounted device. I guess my understanding of EBS is lacking hence I'm unable to distinguish.
Why choose S3 over EFS? They both store files, scale and are replicated. I guess with S3 you have to use the SDK where as with EFS being a file system you can you standard I/O methods from your programming language of choice to create files. But is that the only real difference?
Answer
One word answer: MONEY :D
1 GB to store in US-East-1: (Updated at 2016.dec.20)
- Glacier: $0.004/Month (Note: Major price cut in 2016)
- S3: $0.023/Month
- S3-IA (announced in 2015.09): $0.0125/Month (+$0.01/gig retrieval charge)
- EBS: $0.045-0.1/Month (depends on speed - SSD or not) + IOPS costs
- EFS: $0.3/Month
Further storage options, which may be used for temporary storing data while/before processing it:
- SNS
- SQS
- Kinesis stream
- DynamoDB, SimpleDB
The costs above are just samples. There can be differences by region, and it can change at any point. Also there are extra costs for data transfer (out to the internet). However they show a ratio between the prices of the services.
There are a lot more differences between these services:
EFS is:
- Generally Available (out of preview), but may not yet be available in your region
- Network filesystem (that means it may have bigger latency but it can be shared across several instances; even between regions)
- It is expensive compared to EBS (~10x more) but it gives extra features.
- It's a highly available service.
- It's a managed service
- You can attach the EFS storage to an EC2 Instance
- Can be accessed by multiple EC2 instances simultaneously
- Since 2016.dec.20 it's possible to attach your EFS storage directly to on-premise servers via Direct Connect. ()
EBS is:
- A block storage (so you need to format it). This means you are able to choose which type of file system you want.
- As it's a block storage, you can use Raid 1 (or 0 or 10) with multiple block storages
- It is really fast
- It is relatively cheap
- With the new announcements from Amazon, you can store up to 16TB data per storage on SSD-s.
- You can snapshot an EBS (while it's still running) for backup reasons
- But it only exists in a particular region. Although you can migrate it to another region, you cannot just access it across regions (only if you share it via the EC2; but that means you have a file server)
- You need an EC2 instance to attach it to
- New feature (2017.Feb.15): You can now increase volume size, adjust performance, or change the volume type while the volume is in use. You can continue to use your application while the change takes effect.
S3 is:
- An object store (not a file system).
- You can store files and "folders" but can't have locks, permissions etc like you would with a traditional file system
- This means, by default you can't just mount S3 and use it as your webserver
- But it's perfect for storing your images and videos for your website
- Great for short term archiving (e.g. a few weeks). It's good for long term archiving too, but Glacier is more cost efficient.
- Great for storing logs
- You can access the data from every region (extra costs may apply)
- Highly Available, Redundant. Basically data loss is not possible (99.999999999% durability, 99.9 uptime SLA)
- Much cheaper than EBS.
- You can serve the content directly to the internet, you can even have a full (static) website working direct from S3, without an EC2 instance
Glacier is:
- Long term archive storage
- Extremely cheap to store
- Potentially very expensive to retrieve
- Takes up to 4 hours to "read back" your data (so only store items you know you won't need to retrieve for a long time)
As it got mentioned in JDL's comment, there are several interesting aspects in terms of pricing. For example Glacier, S3, EFS allocates the storage for you based on your usage, while at EBS you need to predefine the allocated storage. Which means, you need to over estimate. ( However it's easy to add more storage to your EBS volumes, it requires some engineering, which means you always "overpay" your EBS storage, which makes it even more expensive.)
Source: AWS Storage Update – New Lower Cost S3 Storage Option & Glacier Price Reduction