AWS Storage Flashcards
Object Storage
Ex. Amazon S3
manage data as individual objects, rather than as blocks and sectors (block-based) or a file hierarchy (file-based)
accessed using a REST API (URL w/ HTTP methods like GET, PUT)
each object includes the data itself, metadata (data about the data), and globally unique identifier
due to its flat file structure, object storage has virtually unlimited scalability and allows the retention of massive amounts of unstructured data
Block Storage
Ex. Amazon Elastic Block Store (EBS)
data is stored and managed in blocks within sectors and tracks
controlled by a server-based operating system
volumes appear as local disks to the operating systems and can be partitioned and formatted
you can use block storage devices as a boot volume
Use Cases: structured information
ie - file systems, databases, transactional logs, SQL databases and virtual machines (VMs)
File Storage
Ex. Amazon Elastic File System
file based storage system manage data in a file hierarchy
file system is mounted via the network to a client computer where it then becomes accessible for reading and writing data
protocols used for accessing file systems include NFS or CIFS/SMB
Amazon Simple Storage Service (S3)
Object-based storage system; an object is just a file, which is uploaded into buckets
object storage built to store and retrieve any amount of data from anywhere - web sites and mobile apps, corporate applications, and data from IoT sensors or devices
you can store any type of file in S3
S3 is designed to deliver 99% durability
Use Cases: backup & storage, application hosting, media hosting, software delivery, static website
Files & Buckets
Buckets:
files are stored in buckets
buckets are root level folders; you can’t create buckets within buckets
S3 is a universal namespace so bucket names must be unique globally
you create your buckets within a region, so you’re data stays within regions
it is a best practice to create buckets in regions that are physically closest to your users to reduce latency
files can be anywhere from 0 bytes to 5 TB
Objects (consist of….)
Consist of:
- key (name of the object)
- value (data made up of a sequence of bytes)
- version ID (used for versioning)
- metadata (data about the data that is stored)
Amazon S3 Storage Class:
S3 Standard
S3 Storage Class (6 total)
durable, immediately available, frequently accessed
Amazon S3 Storage Class:
S3 Intelligent-Tiering
S3 Storage Class (6 total)
automatically moves data to the most cost effective tier
Amazon S3 Storage Class:
S3 Standard-IA
S3 Storage Class (6 total)
means infrequently accessed; durable, immediately available, infrequently accessed data
Amazon S3 Storage Class:
S3 One-Zone-IA
S3 Storage Class (6 total)
lower cost for infrequently accessed data with less resilience
Amazon S3 Storage Class:
S3 Glacier
S3 Storage Class (6 total)
archived data, retrieval times in minutes or hours
Amazon S3 Storage Class:
S3 Glacier Deep Archive
S3 Storage Class (6 total) lowest cost storage class for long term retention
Amazon S3 Additional Features:
Transfer Acceleration
Transfer Acceleration - speed up data uploads using CloudFront in reverse
S3 Versioning
maintains multiple variants of an object in the same bucket
can be used to preserve, retrieve, and restore every version of every object in an S3 bucket
can be enabled at any time
once enabled can be suspended
Versioning should be enabled in source and destination buckets
S3 Replication
You can replicate objects between different AWS Regions or within the same AWS region - Cross-Region Replication (CRR) and Same-Region Replication (SRR)
Why use replication?
meet compliance requirements for storing data at greater distances (CRR)
minimize latency for users who are closer to another AWS Region (CRR)
backup copy of your data in another AWS Region (CRR)
copy the objects to another S3 storage class
aggregate logs into a single bucket
How
enable the AWS Region in account
Enable versioning on source and destination buckets
Ensure S3 has permissions to both buckets
Configure replication