Bird
Raised Fist0
AWScloud~5 mins

CLI scripting basics in AWS - Time & Space Complexity

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Time Complexity: CLI scripting basics
O(n)
Understanding Time Complexity

When using AWS CLI scripts, it is important to understand how the time to complete tasks grows as you add more commands or resources.

We want to know how the number of AWS commands affects the total time taken.

Scenario Under Consideration

Analyze the time complexity of this AWS CLI script sequence.


aws s3 mb s3://my-bucket
for i in $(seq 1 100); do
  aws s3 cp file${i}.txt s3://my-bucket/
  aws ec2 start-instances --instance-ids i-1234567890abcdef0
  aws ec2 stop-instances --instance-ids i-1234567890abcdef0
 done

This script creates a bucket, then uploads 100 files and starts and stops an EC2 instance 100 times.

Identify Repeating Operations

Look at the repeated AWS CLI commands in the script.

  • Primary operation: Uploading files and starting/stopping instances.
  • How many times: Each upload and start/stop command runs 100 times.
How Execution Grows With Input

As the number of files or instance operations increases, the total commands grow proportionally.

Input Size (n)Approx. Api Calls/Operations
10~30 (10 uploads + 10 starts + 10 stops)
100~300 (100 uploads + 100 starts + 100 stops)
1000~3000 (1000 uploads + 1000 starts + 1000 stops)

Pattern observation: The total commands increase directly with the number of files or operations.

Final Time Complexity

Time Complexity: O(n)

This means the total time grows in direct proportion to the number of repeated commands.

Common Mistake

[X] Wrong: "Adding more files won't affect total time much because commands run fast."

[OK] Correct: Each command takes time, so more commands add up linearly, increasing total time noticeably.

Interview Connect

Understanding how script length affects execution time helps you write efficient automation and shows you can think about scaling tasks.

Self-Check

"What if we changed the script to upload files in parallel instead of sequentially? How would the time complexity change?"

Practice

(1/5)
1. What does the AWS CLI command aws s3 ls do?
easy
A. Deletes all S3 buckets in your AWS account
B. Creates a new S3 bucket
C. Lists all S3 buckets in your AWS account
D. Uploads a file to an S3 bucket

Solution

  1. Step 1: Understand the command structure

    The command uses aws s3 which relates to the S3 service, and ls which means list.

  2. Step 2: Interpret the command action

    Listing in S3 context means showing all buckets or objects. Without extra parameters, it lists all buckets.

  3. Final Answer:

    Lists all S3 buckets in your AWS account -> Option C

  4. Quick Check:

    Command aws s3 ls lists buckets [OK]
Hint: Remember: 'ls' means list, so it shows existing resources [OK]
Common Mistakes:
  • Confusing 'ls' with 'rm' (delete)
  • Thinking it creates resources
  • Assuming it uploads files
2. Which of the following is the correct syntax to create an EC2 instance using AWS CLI?
easy
A. aws ec2 run-instances --image-id ami-12345678 --count 1
B. aws ec2 create-instance --image-id ami-12345678 --count 1
C. aws ec2 start-instance --image-id ami-12345678 --count 1
D. aws ec2 launch-instance --image-id ami-12345678 --count 1

Solution

  1. Step 1: Identify the correct AWS CLI command for EC2 instance creation

    The official command to create EC2 instances is run-instances.

  2. Step 2: Check the syntax correctness

    aws ec2 run-instances --image-id ami-12345678 --count 1 uses aws ec2 run-instances --image-id ami-12345678 --count 1, which is the correct syntax to launch one instance.

  3. Final Answer:

    aws ec2 run-instances --image-id ami-12345678 --count 1 -> Option A

  4. Quick Check:

    EC2 instance creation uses 'run-instances' command [OK]
Hint: Use 'run-instances' to launch EC2, not 'create-instance' [OK]
Common Mistakes:
  • Using 'create-instance' which is invalid
  • Confusing 'start-instance' with creation
  • Using 'launch-instance' which is not a valid command
3. What will be the output of this AWS CLI command?
aws s3api list-buckets --query 'Buckets[].Name' --output json
medium
A. A JSON array of bucket names
B. A list of bucket creation dates
C. An error because of wrong syntax
D. A plain text list of bucket names

Solution

  1. Step 1: Understand the command components

    The command uses list-buckets to get all buckets, with a query to extract only the bucket names.

  2. Step 2: Analyze the output format

    The --output json option formats the result as JSON, so the output is a JSON array of bucket names.

  3. Final Answer:

    A JSON array of bucket names -> Option A

  4. Quick Check:

    Query filters names, output json formats as JSON array [OK]
Hint: Query filters data, output json formats it as JSON [OK]
Common Mistakes:
  • Expecting plain text instead of JSON
  • Confusing bucket names with creation dates
  • Assuming syntax error due to query
4. You run this command to delete an S3 bucket:
aws s3 rb s3://my-bucket

But it fails with an error. What is the most likely cause?
medium
A. You need to use aws s3 rm instead
B. The bucket is not empty
C. The bucket name is invalid
D. The AWS CLI is not installed

Solution

  1. Step 1: Understand the command purpose

    aws s3 rb removes (deletes) an S3 bucket, but only if it is empty.

  2. Step 2: Identify the common error cause

    If the bucket contains files, the command fails. You must delete all objects first.

  3. Final Answer:

    The bucket is not empty -> Option B

  4. Quick Check:

    Bucket must be empty before removal [OK]
Hint: Empty bucket before deleting with 'rb' command [OK]
Common Mistakes:
  • Trying to delete non-empty bucket directly
  • Confusing 'rm' (remove objects) with 'rb' (remove bucket)
  • Assuming AWS CLI is not installed without checking
5. You want to write a script that lists all EC2 instances and then stops each one. Which AWS CLI commands should you combine in the script?
hard
A. Use aws ec2 show-instances to list, then aws ec2 power-off-instances to stop
B. Use aws ec2 list-instances to list, then aws ec2 terminate-instances to stop
C. Use aws ec2 get-instances to list, then aws ec2 shutdown-instances to stop
D. Use aws ec2 describe-instances to list, then aws ec2 stop-instances --instance-ids to stop

Solution

  1. Step 1: Identify the correct command to list EC2 instances

    The correct command to list instances is describe-instances.

  2. Step 2: Identify the correct command to stop instances

    To stop instances, use stop-instances with the instance IDs.

  3. Step 3: Combine commands in script logic

    First list instances to get IDs, then stop them using those IDs.

  4. Final Answer:

    Use aws ec2 describe-instances to list, then aws ec2 stop-instances --instance-ids to stop -> Option D

  5. Quick Check:

    List with describe, stop with stop-instances [OK]
Hint: List with 'describe-instances', stop with 'stop-instances' [OK]
Common Mistakes:
  • Using non-existent commands like 'list-instances'
  • Confusing 'terminate' with 'stop' (termination deletes)
  • Using wrong commands that cause errors