Why Basic CLI commands (s3, ec2) in AWS? - Purpose & Use Cases

The Big Idea

What if you could manage your cloud servers and storage faster than clicking through endless web pages?

The Scenario

Imagine you want to upload files to your cloud storage or start a virtual server by clicking through many web pages and forms every time.

It feels like filling out long paperwork repeatedly for simple tasks.

The Problem

Doing these tasks manually is slow and tiring.

You might click the wrong button or forget a step, causing errors or delays.

It's hard to repeat the same steps exactly each time, especially when managing many files or servers.

The Solution

Using basic CLI commands lets you type simple instructions to manage storage and servers quickly.

This saves time, reduces mistakes, and lets you automate repetitive tasks easily.

Before vs After

✗ Before

Open browser > Navigate to S3 > Click upload > Select file > Confirm

✓ After

aws s3 cp file.txt s3://mybucket/

What It Enables

You can control cloud storage and servers instantly from your keyboard, making your work faster and more reliable.

Real Life Example

A developer quickly uploads new website files to S3 and launches a test server with a few typed commands instead of waiting through multiple web pages.

Key Takeaways

Manual cloud tasks are slow and error-prone.

CLI commands simplify and speed up managing cloud storage and servers.

They enable automation and consistent results.

Practice

1. Which AWS CLI command lists all buckets in Amazon S3?

easy

A. aws s3 list-buckets

B. aws ec2 ls

C. aws ec2 describe-buckets

D. aws s3 ls

Solution

1. Step 1: Understand the service for buckets

   Amazon S3 stores buckets, so the command must use aws s3.

2. Step 2: Identify the correct action to list buckets

   The ls action lists buckets in S3. So aws s3 ls lists all buckets.

3. Final Answer:

   aws s3 ls -> Option D

4. Quick Check:

   List buckets = aws s3 ls [OK]

Hint: Use 'aws s3 ls' to list buckets quickly [OK]

Common Mistakes:

• Confusing EC2 commands with S3 commands
• Using 'list-buckets' which is not a valid CLI action
• Trying to list buckets with 'aws ec2' commands

2. Which command correctly starts an EC2 instance with ID i-1234567890abcdef0?

easy

A. aws ec2 start-instances --instance-ids i-1234567890abcdef0

B. aws ec2 start-instance --instance-ids i-1234567890abcdef0

C. aws ec2 start-instances --instance-id i-1234567890abcdef0

D. aws ec2 start-instance --instance-id i-1234567890abcdef0

Solution

1. Step 1: Identify the correct EC2 start command

   The correct command to start instances is start-instances (plural).

2. Step 2: Use the correct option name for instance IDs

   The option is --instance-ids (plural), not --instance-id.

3. Final Answer:

   aws ec2 start-instances --instance-ids i-1234567890abcdef0 -> Option A

4. Quick Check:

   Start instances = start-instances + --instance-ids [OK]

Hint: Use plural 'start-instances' and '--instance-ids' options [OK]

Common Mistakes:

• Using singular 'start-instance' instead of 'start-instances'
• Using '--instance-id' instead of '--instance-ids'
• Mixing up EC2 and S3 commands

3. What is the output of this command if the bucket my-bucket contains two files file1.txt and file2.txt?

aws s3 ls s3://my-bucket/

medium

A. Lists the names and sizes of file1.txt and file2.txt

B. Shows an error: bucket not found

C. Lists only the bucket name my-bucket

D. Deletes the files in the bucket

Solution

1. Step 1: Understand the command purpose

   aws s3 ls s3://my-bucket/ lists objects inside the bucket my-bucket.

2. Step 2: Predict the output for files in the bucket

   The command will show the file names and their sizes for file1.txt and file2.txt.

3. Final Answer:

   Lists the names and sizes of file1.txt and file2.txt -> Option A

4. Quick Check:

   List bucket contents = file names + sizes [OK]

Hint: Use 'aws s3 ls s3://bucket/' to list files inside [OK]

Common Mistakes:

• Thinking it lists buckets instead of files
• Expecting deletion or error output
• Confusing bucket name listing with object listing

4. You run this command but get an error: aws ec2 describe-instances --instance-ids i-1234567890abcdef0. What is the likely cause?

medium

A. The command should be aws s3 describe-instances

B. The instance ID is incorrect or does not exist

C. You must use start-instances instead of describe-instances

D. You forgot to add --bucket option

Solution

1. Step 1: Check command correctness

   aws ec2 describe-instances --instance-ids is a valid command to get instance details.

2. Step 2: Identify common error reasons

   An error usually means the instance ID is wrong or the instance does not exist in your account or region.

3. Final Answer:

   The instance ID is incorrect or does not exist -> Option B

4. Quick Check:

   Invalid instance ID causes describe-instances error [OK]

Hint: Check instance ID spelling and region for describe-instances errors [OK]

Common Mistakes:

• Using S3 commands for EC2 tasks
• Confusing describe with start commands
• Adding irrelevant options like --bucket

5. You want to copy a local file photo.jpg to an S3 bucket my-photos in a folder 2024/. Which command correctly does this?

hard

A. aws ec2 cp photo.jpg s3://my-photos/2024/

B. aws s3 mv photo.jpg s3://my-photos/2024/

C. aws s3 cp photo.jpg s3://my-photos/2024/

D. aws s3 sync photo.jpg s3://my-photos/2024/

Solution

1. Step 1: Choose the correct AWS service and action

   Copying files to S3 uses aws s3 cp. EC2 commands do not handle S3 files.

2. Step 2: Use the correct source and destination syntax

   Source is local file photo.jpg, destination is S3 path s3://my-photos/2024/.

3. Final Answer:

   aws s3 cp photo.jpg s3://my-photos/2024/ -> Option C

4. Quick Check:

   Copy local file to S3 = aws s3 cp [OK]

Hint: Use 'aws s3 cp' to copy files to S3 buckets [OK]

Common Mistakes:

• Using 'mv' which moves instead of copies
• Using 'sync' for single file copy
• Using EC2 commands for S3 file operations