AWS - S3 Flashcards

1
Q

What is the blast radius of an S3 bucket?

A

A Region. S3 is regionally resilient.

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

S3 bucket naming restrictions?

A
  • Name has to be globally unique (across all regions and all AWS accounts)
  • Names are between 3 and 63 lowercase characters with no underscores
  • Have to start with a character or number
  • Can’t be formatted like an IP address (1.1.1.1)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Max number of buckets per account?

A

Soft limit of 100 buckets per account. You can make support requests to get this increased up to the hard limit of 1000.

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

Max individual object size in a bucket?

A

Objects can be from 0 to 5TB each

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

How does S3 versioning work?

A
  • Configured at the bucket level.
  • Once enabled, you can never disable.
  • However, you can suspend it, then unsuspend (back to Enabled)
  • Objects have an ID. When versioning is off, ID always equals null.
  • AWS keeps track of the Latest Version / Current Version.
  • When you delete, AWS just hides the object and adds a Delete marker.
  • You can delete the Delete Marker to un-delete the object.
  • You are charged storage for all versions.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Can you hard-delete an object in a bucket that has versioning turned on?

A

You can hard-delete a specific object version by specifying the object ID. If you delete the latest, the previous becomes the current version.

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

How does the S3 Multi-Part Upload feature work?

A
  • Breaks an object up into chunks and uploads chunks in parallel.
  • Data has to be >= 100MB to use multipart upload
  • Max of 10,000 upload parts
  • 5MB to 5GB per part
  • Each individual part can be re-uploaded independently
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

How does S3 Accelerated Transfer work?

A
  • You turn it on per bucket
  • When turned on, your public internet-connected device gets connected to the nearest Edge Location for the upload
  • AWS then transfers the file from this edge location through the AWS global network to the AWS destination region (rather than over the public internet).

What’s the alternative?
- By default, ISPs route traffic between points based on what is relatively fast but also economical for them.

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

Restrictions for turning on Accelerated Transfer on a bucket?

A
  • The bucket name cannot contain periods in its name.
  • The bucket name has to be DNS compatible.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is S3 SEC-C?

A

Server-Side Encryption with Customer-Provided Keys
- You send the raw data + a key to S3.
- S3 encrypts it and stores the encrypted data plus a hash of the data.
- S3 discards the key - doesn’t store them.
- To decrypt, you send the key again

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

What is SEC-S3?

A

SSE-S3: Server-Side Encryption with Amazon S3-Managed Keys
- (uses AES256)
- S3 generates a key for just this one object.
- After encrypting the object, the S3 Root Key is used to encrypt that one unique key, then discards the unencrypted copy
- The encrypted data and encrypted key are stored.

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

Pros and Cons of S3 SEC-S3?

A

Pros:
- Lowest overhead method.

Cons:
- May not meet regulatory compliance for you.
- You can’t separate permissions / No Role Separation. A full S3 Admin would have access to decrypt the data.

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

What is S3 SSE-KMS?

A

Server-Side Encryption with KMS Keys stored in AWS KMS
- AWS generates and uses a default key in KMS to encrypt the DEK.
- However, you can create your own KMS key.
- And you can use CloudTrail to see any activity.

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

What is S3 Client-Side Encryption?

A
  • Data is encrypted within the client before any transfer happens
  • Guarantees that there is no possibly way AWS could ever see or interact with the un-encrypted data
  • You have more responsibility: you are responsible for encrypting properly; you also have to take care of the decryption
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is S3 Server-Side Encryption and what are the 3 options?

A
  • S3 does the encryption prior to storing for you
    Options:
    1. SSE-C
    2. SSE-S3
    3. SSE-KMS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the 3 high-level S3 Storage Classes?

A
  • S3 Standard
  • S3 Glacier
  • S3 Intelligent-Tiering
17
Q

What are the 3 flavors of S3 Standard?

A
  • S3 Standard
    • Auto Replicated across at least 3 AZs within the region
    • Provides 11 9’s of durability
    • First-byte retrieval within milliseconds
  • S3 Standard-IA (Infrequent Access)
    • Good if you only need the data, say, once a month
    • About half the cost for storage as Standard
    • Not good for lots of tiny records.
  • S3 One Zone-IA
    • Cheaper than both the above
    • Exactly the same as Standard-IA, except:
      • Only stored in one AZ
      • Still get 11 9’s of availability so long as your AZ doesn’t die.
18
Q

What are the 3 flavors of S3 Glacier?

A
  • S3 Glacier - Instant Retrieval
    > Good if you only need the data, say, once a quarter
    • cheaper storage
    • more expensive retrieval
    • longer minimum storage: 90 days
  • S3 Glacier - Flexible Retrieval
    • Cold… not ready for use
    • First-byte latency of minutes to hours
    • You have to kick off a job to pull these out of cold storage
  • S3 Glacier - Deep Archive
    • Frozen…
    • 40KB minimum size, 180 day min duration
19
Q

How does S3 Intelligent-Tiering work?

A
  • You don’t have to worry about moving between options.
  • Good for situations where the usage frequency is unknown or it changes over time.
  • If not accessed for 30 days, it gets moved to Infrequent
  • 90 days: moves to Archive Instant Access
  • Next two tiers are optional. Can be configured to be used for:
    • Archive: objects aren’t accessed for 90-270 days
    • Deep Archive: objects aren’t accessed for 180 to 730 days