Techniques

• S3 can host static websites and have them accessible on the Internet

• The website URL will be (depending on the region)

• If you get a 403 Forbidden error, make sure the bucket policy allows public reads!

• You can version your files in Amazon S3

• It is enabled at the bucket level

• Same key overwrite will change the “version”: 1, 2, 3....

• It is best practice to version your buckets

• Notes:

Any file that is not versioned prior to enabling versioning will have version “null”
Suspending versioning does not delete the previous versions

• Must enable Versioning in source and destination buckets

• Cross-Region Replication (CRR)

• Same-Region Replication (SRR)

• Buckets can be in different AWS accounts

• Copying is asynchronous

• Must give proper IAM permissions to S3

• Use cases:

CRR – compliance, lower latency access, replication across accounts
SRR – log aggregation, live replication between production and test accounts

• Amazon S3 Standard - General Purpose

• Amazon S3 Standard-Infrequent Access (IA)

• Amazon S3 One Zone-Infrequent Access

• Amazon S3 Glacier Instant Retrieval

• Amazon S3 Glacier Flexible Retrieval

• Amazon S3 Glacier Deep Archive

• Amazon S3 Intelligent Tiering

• Can move between classes manually or using S3 Lifecycle configurations

• Durability:

High durability (99.999999999%, 11 9’s) of objects across multiple AZ
If you store 10,000,000 objects with Amazon S3, you can on average expect to incur a loss of a single object once every 10,000 years
Same for all storage classes

• Availability:

99.99% Availability
Used for frequently accessed data
Low latency and high throughput
Sustain 2 concurrent facility failures
Use Cases: Big Data analytics, mobile & gaming applications, content distribution...

• For data that is less frequently accessed, but requires rapid access when needed

• Lower cost than S3 Standard

• Amazon S3 Standard-Infrequent Access (S3 Standard-IA)

• Amazon S3 One Zone-Infrequent Access (S3 One Zone-IA)

High durability (99.999999999%) in a single AZ; data lost when AZ is destroyed
99.5% Availability
Use Cases: Storing secondary backup copies of on-premise data, or data you can recreate