S3 Flashcards

1
Q

What can S3 do?

A
  • upload any file type
    ex: photos, videos, code, documents
  • CANNOT run an OS or database
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

S3 Basics (limits)

A
  • unlimited storage (total volume)*

- objects can be up to 5 TB in size*

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Buckets

A
  • must have a universal namespace (be globally unique)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

S3 URLs*

A

https: //bucket-name.s3.region.amazonaws.com/key-name
https: // + bucket name + .s3 + .region + /filename

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Successful CLI or API uploads

A

Return a 200 http code

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

S3 key-value store

A

key: the name of the object (ex: beach.jpg)
value: the data itself (sequency of bytes) *
Version ID: for storing multiple versions*
Metadata: data about the data (content-type, last-modified, etc.)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

S3 Availability

A

99.95 - 99.99% service availability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

S3 Durability

A

99.999999999% durability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

S3 Standard

A
  • Stored in >= 3 AZs
  • 99.99% availability
  • 11 9’s durability
  • for frequent access
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

S3 Standard Use Cases

A
  • websites
  • gaming apps
  • big data analytics
  • content distribution
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Ways to secure S3 data

A

1) server-side encryption
2) access control lists (ACLs): can attach to a bucket or individual objects
3) bucket policies

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Bucket Policy

A

JSON policies that apply to the bucket as a whole (& bucket contents)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

S3 Consistency Model: Strong-Read-After-Write *

A

after a successful write of a new object or overwrite of an existing object, any subsequent request immediately receives the latest version.
- you can immediately perform a List to get all objects in a bucket with all changes reflected

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Object ACL

A

applies to individual objects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Bucket details*

A
  • S3 is a global view, but buckets are regional

- by default buckets and objects are private until you unblock access to them*

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the use cases of S3 static websites?

A

For webpages that don’t require a database connection

- pages can also contain client-side scripts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Benefits of S3 static website?

A

Scales automatically to meet demand

ex: a movie trailer website. Many enterprises put static sites on S3 when there will be a lot of demand

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

How to make an S3 website public?*

A

Using a bucket policy*

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

S3 versioning

A
  • all versions are stored, even if you delete an object*
  • cannot be disabled once enabled, only suspended*
  • can be integrated with lifecycle rules
  • Supports MFA*
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Why use MFA for object deletion?

A

to protect objects from deleting, require 2 forms of authentication

21
Q

public vs private with versioning

A

only the most-recent version is public - everything else is restricted, unless explicitly made public

22
Q

How do you restore an S3 object that has been deleted?

A

deleting objects adds a ‘delete marker’ to them. to restore the object, delete the delete marker

23
Q

Which S3 storage class is cost-optimized for unknown access patterns?

A

S3 Intelligent Tiering

24
Q

Which S3 storage class costs the most?

A

S3 Standard

25
Q

Which storage classes have a retrieval fee?

A

S3 Infrequent Access
S3 OneZone-IA
S3 Glacier
S3 Glacier Deep Archive

26
Q

Old Glacier SLAs

A

Glacier = archive < 12 hrs

Glacier Deep archive > 12 hours

27
Q

S3 Lifecycle Management

A
  • automates moving your objects between the different storage tiers, maximizing cost effectiveness
  • Ex: move from S3 -> S3 IA -> Glacier (can configure how many days between each jump)
28
Q

How do you combine Lifecycle Management with Versioning?

A

there’s a lifecycle configuration on the bucket management tab > select “Lifecycle Rule” with Transitions

29
Q

S3 Object Lock

A

Prevents objects from being deleted or modified

  • for a fixed amount of time, or indefintely
  • if you see WORM in an S3 question, use Object Lock
  • can be applied at bucket or object level
30
Q

WORM model

A

W - Write
O - Once
R - Read
M - Many

31
Q

Use case for Object Lock

A
  • regulatory requirements

- extra layer of protections against changes or deletions

32
Q

S3 Object Lock: Governance Mode*

A

requires special permissions to overwrite, delete, or alter lock settings
some users can alter and delete

33
Q

S3 Object Lock: Compliance Mode*

A

nobody can alter the object, including root user

- for a specific retention period

34
Q

S3 Object Lock : Retention Period

A

a timestamp in metadata indicating when the retention period expires

35
Q

S3 Object Lock: Legal Hold

A

prevents object version from being overwritten or deleted

- remains in effect until the flag is removed

36
Q

What permission do you need to remove a legal hold?

A

S3: PutObjectLegalHold

37
Q

Glacier Vault Lock*

A

a way of applying a WORM model to Glacier

38
Q

S3 Encryption in transit*

A

uses https

the “s” = SSL/TSL certificate

39
Q

S3 Encryption at rest*

A

Server-Side encryption
A) SSE-S3: S3 manages your keys (AES 256 bit)
B) SSE-KMS: KMS manages your keys
C) SSE-C: Customer (you) manage the keys

40
Q

S3 Client-Side Encryption*

A

you encrypt the files yourself before uploading to S3

41
Q

2 ways to apply encryption to S3

A

1) via the console
2) using a bucket policy*
- - denies any PUT request that doesn’t include the x-amz-server-side-encryption parameter in the request header

42
Q

S3 Prefixes*

A

folders inside S3 buckets
ex: mybucketname/folder1/subfolder1/file.jpg
prefix = /folder1/subfolder1

43
Q

S3 Performance*

A

Extremely low latency

  • the more prefixes, the better the latency*
  • 3500 PUT/COPY/POST/DELETE per second, per prefix
  • 5,500 GET/HEAD per second, per prefix

ex: 2 prefixes = 11,000 request per second
4 prefixes = 22,000 requests per second

44
Q

S3 Limitations with KMS*

A

KMS has built in limits on SSE-KMS

  • limits are region specific: 5,500, 10,000 or 30,000 requests per second
  • uploads and downloads count toward the limit
  • on exam, it may be best to use SSE-S3 instead. *
45
Q

S3 Performance Uploads

A

Multi-Part uploads -> parallelize uploads

  • increases efficiency
  • required for files over 5 GB
  • recommended for files over 100 MB
46
Q

S3 Performance Downloads

A

S3 Byte-Range fetches

  • parallelize downloads by specifying byte ranges
  • can be used to speed up downloads
  • can be used to download partial amounts of the file (eg. header info)
47
Q

S3 Replication for Backing Up

A
  • previously called cross-region replication*
  • a way of replicating objects from one bucket to another*
  • versioning must be enabled on both buckets for this to work*
48
Q

Turn on S3 Replication

A

1) create 2 new buckets
2) turn on replication for both
3) upload all the files to one bucket
4) delete markers are not replicated by default*
(your replication bucket can have a different storage class to save money)