Chapter 5.1 - S3 Overview

Question 1

What does S3 stand for?

Answer 1

Simple Storage Service

Question 2

What type of storage is S3?

Answer 2

Object-based storage.
“Flat files” that don’t change, such as text documents, videos, websites, etc.
Databases are NOT flat files.

Question 3

What are the basic characteristics of S3?

Answer 3

• Object-based
• File size of 0 Bytes to 5 TB
• Unlimited storage
• Files stored in Buckets (aka Folder, Directory, etc)
• Uses “Universal Namespace”. The name must be unique globally.
• Successful upload of a file will result in a “HTTP 200 code”

Question 4

How are S3 Objects identified?

Answer 4

S3 Objects are identified by Key:Value Pairs with the Key being the name of the object and the Value being the data in a sequence of bytes.

They will also contain a Version ID, Metadata and Subresources such as Access Control Lists and Torrents.

Question 5

How is Data Consistency handled for S3?

Answer 5

Read after Write consistency for PUTS of NEW Objects is:
Immediate Read after Write

Eventual Consistency for OVERWRITE PUTS and DELETES:
Can take some time to propagate (few seconds)
May NOT be able to Read immediately after Write.
May STILL be able to Read after Delete.

Question 6

What are the basic features of S3?

Answer 6

• Tiered Storage Available
• Lifecycle Management
• Versioning
• Encryption
• Secure data using Server-Side Encryption, Access Control Lists and Bucket Policies
  *Data Consistency Model
  *After a successful write of a new object (PUT) or an overwrite of an existing object, any subsequent read request immediately
  receives the latest version of the object.
  Strong consistency for list operations, so after a write, you can immediately perform a listing of the objects in a bucket with all changes reflected.

Question 7

What are the basic features of S3?

Answer 7

• Tiered Storage Available
• Lifecycle Management
• Versioning
• Encryption
• Secure data using Server-Side Encryption, Access Control Lists and Bucket Policies
  *Data Consistency Model
  
  • After a successful write of a new object (PUT) or an overwrite of an existing object, any subsequent read request immediately
    receives the latest version of the object.
  • Strong consistency for list operations, so after a write, you can immediately perform a listing of the objects in a bucket with all
    changes reflected.