S3 Flashcards

1
Q

s3 bucket name

A

globally unique name

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

Buckets are defined

A

region level

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

key is the FULL path

A
  • s3://my-bucket/my_file.txt

* s3://my-bucket/my_folder1/another_folder/my_file.txt

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

key is composed of prefix + object name

A

s3://my-bucket/my_folder1/another_folder/my_file.txt

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

Amazon S3 - Versioning

A

bucket level

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

best practice to version your buckets

A

Protect against unintended deletes

Easy roll back to the previous version

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

4 methods of encrypting objects in S3

A

SSE-S3: encrypts S3 objects using keys handled & managed by AWS

SSE-KMS: leverage AWS Key Management Service to manage encryption keys

SSE-C: when you want to manage your own encryption keys

Client-Side Encryption

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

SSE-S3

A

keys handled & managed by Amazon S3
encrypted server-side

“x-amz-server-side-encryption”: “AES256”

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

SSE-KMS

A

encryption using keys handled & managed by KMS

KMS Advantages: user control + audit trail

encrypted server-side

“x-amz-server-side-encryption”: ”aws:kms”

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

SSE-C

A

server-side encryption
keys fully managed by the customer outside of AWS
S3 does not store the encryption key
HTTPS must be used

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

Client Side Encryption

A

Encryption and decryption at client side

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

HTTPS endpoint

A

encryption in flight

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

Block public and cross-account access to buckets and objects
through any public bucket or access point policies

Why this default policy?

A

These settings were created to prevent company data leaks

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

Pre-Signed URLs

A

Very useful for giving temporary access to users.

URLs that are valid only for a limited time (ex: premium video
service for logged in users)

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

CORS fulfilled using header

A

CORS Headers (ex: Access-Control-Allow-Origin)

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

S3 CORS

A

If a client does a cross-origin request on our S3 bucket, we need to enable the correct CORS headers.

You can allow for a specific origin or for * (all origins)

17
Q

Cross-Region Replication (CRR)

A

Use cases: compliance, lower latency access,

replication across accounts

18
Q

Upload Files in S3 glacier

A

you must either use the AWS CLI or write code to make requests, by using either the REST API directly or by using the Amazon SDKs

19
Q

What about the read-write consistency of S3??

A

Effective immediately, all S3 GET, PUT, and LIST operations, as well as operations that change object tags, ACLs, or metadata, are now strongly consistent.

What you write is what you will read, and the results of a LIST will be an accurate reflection of what’s in the bucket. This applies to all existing and new S3 objects, works in all regions, and is available to you at no extra charge!

20
Q

Comment on time limit of s3 presigned urls and its expiry

A

s3 presigned urls requires you to change your content urls.
The presigned urls expires after its defined expiration date.

IMP TO NOTE -> There is no feature of s3 signed cookies.

21
Q

CloudFront signed URLs

A

restrict access to individual files

22
Q

CloudFront signed cookies

A

Provide access to multiple signed cookies

23
Q

S3 consistency model

A

1) S3 provides a strong read after write consistency for PUTs and DELETEs.
2) Amazon S3 does not support object locking for concurrent writers.
3) If two put requests are made on the same key, the latest put request wins.
4) Bucket configurations have eventual consistency models like deleting a bucket or enabling versioning.

For more reading on it.
Read the AWS docs on the S3 consistency model.

24
Q

Amazon S3 now provides increased performance

A

3,500 requests per second to add data and 5,500 requests per second to retrieve data