Free tier usage monitoring in AWS - Time & Space Complexity

Time Complexity: Free tier usage monitoring

O(n)

Understanding Time Complexity

We want to understand how the time to check free tier usage grows as we monitor more AWS resources.

How does the number of resources affect the time it takes to gather usage data?

Scenario Under Consideration

Analyze the time complexity of the following AWS CLI commands used to monitor free tier usage.

aws ce get-cost-and-usage \
  --time-period Start=2024-01-01,End=2024-01-31 \
  --granularity MONTHLY \
  --metrics "UsageQuantity" \
  --filter '{"Dimensions":{"Key":"USAGE_TYPE","Values":["FreeTier"]}}'
    

This command fetches usage data filtered for free tier usage over a month.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: AWS Cost Explorer API call to fetch usage data.
• How many times: Once per time period, but internally AWS processes data for each resource and usage type.

How Execution Grows With Input

As the number of AWS resources increases, the data AWS processes grows.

Input Size (number of resources)	Approx. Operations
10	Small data processed quickly
100	More data, longer processing time
1000	Much more data, noticeably longer time

Pattern observation: Time grows roughly in proportion to the number of resources being monitored.

Final Time Complexity

Time Complexity: O(n)

This means the time to get free tier usage grows linearly with the number of resources.

Common Mistake

[X] Wrong: "The command runs in constant time no matter how many resources I have."

[OK] Correct: The AWS backend must process usage data for each resource, so more resources mean more work and longer time.

Interview Connect

Understanding how monitoring scales helps you design efficient cloud cost tracking and shows you can think about system performance in real settings.

Self-Check

"What if we changed the time period from monthly to daily? How would that affect the time complexity?"