Why S3 matters for object storage in AWS - Performance Analysis

Time Complexity: Why S3 matters for object storage

O(n)

Understanding Time Complexity

We want to understand how the time to store and retrieve objects in S3 changes as we add more objects.

How does the number of objects affect the speed of operations?

Scenario Under Consideration

Analyze the time complexity of uploading multiple objects to an S3 bucket.

// Upload multiple files to S3 bucket
for (let i = 0; i < n; i++) {
  s3.putObject({
    Bucket: 'my-bucket',
    Key: `file_${i}.txt`,
    Body: 'file content'
  }, function(err, data) {
    if (err) console.log(err, err.stack); // an error occurred
    else     console.log(data);           // successful response
  });
}

This sequence uploads n separate objects to the same S3 bucket, one by one.

Identify Repeating Operations

• Primary operation: The putObject API call to upload each file.
• How many times: Exactly once per file, so n times for n files.

How Execution Grows With Input

Each new file means one more upload call, so the total work grows directly with the number of files.

Input Size (n)	Approx. Api Calls/Operations
10	10 uploads
100	100 uploads
1000	1000 uploads

Pattern observation: The number of upload operations grows linearly as we add more files.

Final Time Complexity

Time Complexity: O(n)

This means the time to upload all files grows in direct proportion to how many files you have.

Common Mistake

[X] Wrong: "Uploading many files at once takes the same time as uploading one file."

[OK] Correct: Each file requires its own upload call, so more files mean more time overall.

Interview Connect

Understanding how operations scale with input size helps you design efficient storage solutions and explain your reasoning clearly in interviews.

Self-Check

What if we uploaded multiple files in parallel instead of one by one? How would the time complexity change?

Practice

1. What is the main purpose of Amazon S3 in cloud computing?

easy

A. To run virtual servers

B. To store and retrieve files easily

C. To manage databases

D. To monitor network traffic

Solution

1. Step 1: Understand S3's role

   Amazon S3 is designed to store objects like files and data in the cloud.

2. Step 2: Compare with other services

   Unlike servers or databases, S3 focuses on file storage and retrieval.

3. Final Answer:

   To store and retrieve files easily -> Option B

4. Quick Check:

   S3 = File storage [OK]

Hint: S3 is about files, not servers or databases [OK]

Common Mistakes:

• Confusing S3 with compute services
• Thinking S3 manages databases
• Assuming S3 monitors networks

2. Which of the following is the correct way to create a new S3 bucket using AWS CLI?

easy

A. aws s3 mb s3://my-bucket

B. aws s3 make-bucket --name my-bucket

C. aws s3 new-bucket my-bucket

D. aws s3 create-bucket --bucket my-bucket

Solution

1. Step 1: Recall AWS CLI syntax for bucket creation

   The correct command uses 'mb' (make bucket) with the bucket URL.

2. Step 2: Check each option

   aws s3 mb s3://my-bucket matches the correct syntax: 'aws s3 mb s3://my-bucket'. Others are invalid commands.

3. Final Answer:

   aws s3 mb s3://my-bucket -> Option A

4. Quick Check:

   Bucket creation CLI = aws s3 mb [OK]

Hint: 'mb' means make bucket in AWS CLI [OK]

Common Mistakes:

• Using 'create-bucket' instead of 'mb'
• Omitting 's3://' prefix
• Using non-existent commands like 'new-bucket'

3. Given this AWS CLI command:
aws s3 cp file.txt s3://my-bucket/
What happens after running it?

medium

A. Deletes file.txt from the bucket named my-bucket

B. Downloads file.txt from the bucket named my-bucket

C. Uploads file.txt to the bucket named my-bucket

D. Lists contents of my-bucket

Solution

1. Step 1: Understand the 'cp' command in AWS CLI

   'cp' means copy. Here it copies a local file to the S3 bucket.

2. Step 2: Analyze source and destination

   Source is local file 'file.txt', destination is 's3://my-bucket/', so it uploads the file.

3. Final Answer:

   Uploads file.txt to the bucket named my-bucket -> Option C

4. Quick Check:

   aws s3 cp local to s3 = upload [OK]

Hint: 'cp' copies files; source to destination [OK]

Common Mistakes:

• Confusing upload with download
• Thinking 'cp' deletes files
• Assuming it lists bucket contents

4. You tried to upload a file to S3 but got an error: AccessDenied. What is the most likely cause?

medium

A. The AWS CLI is not installed

B. The bucket does not exist

C. The file path is incorrect

D. You lack permission to write to the bucket

Solution

1. Step 1: Understand the AccessDenied error

   This error means the user does not have permission to perform the action.

2. Step 2: Check other options

   Bucket missing causes NotFound error, wrong file path causes file errors, CLI missing causes command errors.

3. Final Answer:

   You lack permission to write to the bucket -> Option D

4. Quick Check:

   AccessDenied = permission issue [OK]

Hint: AccessDenied means permission problem [OK]

Common Mistakes:

• Assuming bucket absence causes AccessDenied
• Blaming file path for permission errors
• Ignoring user permissions

5. You want to store daily backups in S3 and ensure they are not lost accidentally. Which combination of S3 features should you use?

hard

A. Create a bucket with versioning enabled and lifecycle rules to archive old backups

B. Create a bucket without versioning and delete backups after 7 days

C. Use S3 without buckets and store backups locally

D. Create multiple buckets without any backup policies

Solution

1. Step 1: Identify features for backup safety

   Versioning keeps multiple versions to prevent accidental loss. Lifecycle rules manage storage cost by archiving.

2. Step 2: Evaluate options

   Create a bucket with versioning enabled and lifecycle rules to archive old backups uses versioning and lifecycle rules, best for backup safety and cost. Others lack protection or proper management.

3. Final Answer:

   Create a bucket with versioning enabled and lifecycle rules to archive old backups -> Option A

4. Quick Check:

   Versioning + lifecycle = safe backups [OK]

Hint: Enable versioning to protect backups [OK]

Common Mistakes:

• Not enabling versioning risks data loss
• Deleting backups too soon
• Ignoring lifecycle management