Instance states (running, stopped, terminated) in AWS - Time & Space Complexity

Time Complexity: Instance states (running, stopped, terminated)

O(n)

Understanding Time Complexity

When managing cloud instances, it is important to understand how the time to check or change their states grows as you handle more instances.

We want to know how the number of operations changes when we work with many instances in different states.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

# List all instances
aws ec2 describe-instances

# For each instance, check its state
for instance in instances:
  state = instance.state.name
  if state == 'stopped':
    aws ec2 start-instances --instance-ids instance.id

This sequence lists all instances, checks their states, and starts those that are stopped.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Checking each instance's state and starting stopped instances.
• How many times: Once per instance in the list.

How Execution Grows With Input

As the number of instances grows, the number of state checks and possible start commands grows too.

Input Size (n)	Approx. Api Calls/Operations
10	About 10 state checks, up to 10 start commands
100	About 100 state checks, up to 100 start commands
1000	About 1000 state checks, up to 1000 start commands

Pattern observation: The number of operations grows directly with the number of instances.

Final Time Complexity

Time Complexity: O(n)

This means the time to check and start instances grows in a straight line as you add more instances.

Common Mistake

[X] Wrong: "Checking all instances' states takes the same time no matter how many instances there are."

[OK] Correct: Each instance requires a separate check, so more instances mean more checks and more time.

Interview Connect

Understanding how operations grow with the number of instances helps you design efficient cloud management scripts and shows you can think about scaling in real projects.

Self-Check

"What if we batch start stopped instances instead of starting them one by one? How would the time complexity change?"

Practice

1. Which AWS EC2 instance state means the instance is currently powered on and ready to use?

easy

A. Running

B. Stopped

C. Terminated

D. Pending

Solution

1. Step 1: Understand EC2 instance states

   Instances can be in states like running, stopped, or terminated, indicating their power and availability status.

2. Step 2: Identify the state meaning 'powered on'

   The 'running' state means the instance is powered on and ready to use.

3. Final Answer:

   Running -> Option A

4. Quick Check:

   Running = Powered On [OK]

Hint: Running means instance is on and usable [OK]

Common Mistakes:

• Confusing stopped with running
• Thinking terminated means running
• Mixing pending with running

2. Which AWS CLI command correctly stops a running EC2 instance with ID i-1234567890abcdef0?

easy

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

B. aws ec2 reboot-instances --instance-ids i-1234567890abcdef0

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

D. aws ec2 stop-instances --instance-ids i-1234567890abcdef0

Solution

1. Step 1: Identify command to stop instance

   The command to stop an instance is stop-instances.

2. Step 2: Match instance ID usage

   The command must include --instance-ids i-1234567890abcdef0 to specify the instance.

3. Final Answer:

   aws ec2 stop-instances --instance-ids i-1234567890abcdef0 -> Option D

4. Quick Check:

   Stop instance = stop-instances command [OK]

Hint: Stop instance uses 'stop-instances' command [OK]

Common Mistakes:

• Using terminate instead of stop
• Using start instead of stop
• Using reboot instead of stop

3. What will be the state of an EC2 instance immediately after running this AWS CLI command?

aws ec2 terminate-instances --instance-ids i-0abcdef1234567890

medium

A. Running

B. Stopped

C. Terminated

D. Pending

Solution

1. Step 1: Understand the terminate-instances command

   This command deletes the instance permanently, changing its state to terminated.

2. Step 2: Identify the resulting state

   After termination, the instance cannot be started again and is marked as terminated.

3. Final Answer:

   Terminated -> Option C

4. Quick Check:

   Terminate command = Terminated state [OK]

Hint: Terminate means instance is deleted permanently [OK]

Common Mistakes:

• Thinking terminated means stopped
• Confusing terminate with stop
• Expecting instance to restart automatically

4. You tried to start an EC2 instance but got an error saying the instance does not exist. What is the most likely cause?

medium

A. The instance is terminated

B. The instance is in running state

C. The instance is in stopped state

D. The instance is pending

Solution

1. Step 1: Analyze error meaning

   If AWS says the instance does not exist, it usually means it was deleted or terminated.

2. Step 2: Match instance state to error

   Terminated instances are removed and cannot be started again, causing this error.

3. Final Answer:

   The instance is terminated -> Option A

4. Quick Check:

   Instance not found = Terminated state [OK]

Hint: Instance not found means terminated, not stopped [OK]

Common Mistakes:

• Assuming stopped means instance missing
• Confusing running with missing
• Ignoring termination possibility

5. You want to save costs by stopping an EC2 instance but keep its data intact for later use. Which instance state should you use and why?

hard

A. Terminate, because it deletes the instance and saves all costs

B. Stop, because it powers off the instance but keeps data on the disk

C. Running, because it keeps the instance active and data safe

D. Pending, because it prepares the instance for shutdown

Solution

1. Step 1: Understand cost and data retention

   Stopping an instance powers it off but keeps the attached storage intact, preserving data.

2. Step 2: Compare with termination

   Terminating deletes the instance and storage, losing data and cannot be restarted.

3. Step 3: Choose correct state for saving costs and keeping data

   Stopping is the correct choice to save costs while keeping data safe.

4. Final Answer:

   Stop, because it powers off the instance but keeps data on the disk -> Option B

5. Quick Check:

   Stop = Save cost + keep data [OK]

Hint: Stop to save cost and keep data intact [OK]

Common Mistakes:

• Choosing terminate and losing data
• Thinking running saves cost
• Confusing pending with stop