Last active
January 30, 2020 09:52
-
-
Save ross-humphrey/331cb67fced7fa367b3251a9e4344d1a to your computer and use it in GitHub Desktop.
AWS Storage Service Whitepaper Notes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Storage Need and AWS Service Solution | |
Immediate Access - S3 | |
File System - Amazon EFS | |
Structured Data with Query - DynamoDB, RDS, CloudSearch | |
Rapidly Changing Data - EBS, EFS, DynamoDB, RDS, EC2 | |
Archival Data - Amazon Glacier | |
Dynamic Website Hosting - EC2, EFS | |
Temporary Storage - EC2 Local instance store | |
S3 Notes: | |
> 0-5TB of Data | |
3 Storage classes: | |
S3 Standard - general purpose frequently accessed | |
S3 Standard-Infrequent Access (IA) for long lived, but less frequently accessed | |
Glacier - low cost archival data | |
Glacier Notes: | |
> 40 TB limit | |
> Highly secure, druable and flexible storage for archive and backup | |
> When pulling on archives - you initiate a job to pull the archive | |
> Using lifecycle policies you can seamlessly move between Glacier and S3 using S3 Data policies | |
> Can use range retrievals to managed bandwidth costs or targeted part of the archive | |
> Data can be put into locked 'vaults' for regulatory compliance | |
> Take 3-5 hours to pull on data | |
EFS Notes: | |
Simple, scalable, elastic highly available and highly durable NFS as a service to EC2 instances. | |
> Allows for usage across multiple instances | |
> Good for multi threaded applications with concurrent access to data from multiple EC2s | |
> Two different modes; Gneral purpose, if over 7,000 file operations a second use Max I/O performance mode. | |
> EFS is optimized to burst at hight throughput levels for short periods of time | |
> If using a high number of parallel EC2 - EFS is good. | |
> No need to provision in advance |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment