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?"