Cost optimization pillar in AWS - Time & Space Complexity

Time Complexity: Cost optimization pillar

O(n)

Understanding Time Complexity

We want to understand how the cost optimization steps grow as we add more resources or services in AWS.

How does the effort and cost-saving actions scale when managing more cloud resources?

Scenario Under Consideration

Analyze the time complexity of the following cost optimization process.

// Pseudocode for cost optimization actions
for each resource in aws_account_resources:
    analyze_usage(resource)
    recommend_right_sizing(resource)
    check_reserved_instance_eligibility(resource)
    apply_cost_saving_action(resource)
    log_savings(resource)

This sequence reviews each resource to find and apply cost-saving measures.

Identify Repeating Operations

Look at what repeats as the number of resources grows.

• Primary operation: Analyzing and applying cost-saving actions per resource.
• How many times: Once for each resource in the account.

How Execution Grows With Input

As the number of resources increases, the number of cost optimization steps grows directly with it.

Input Size (n)	Approx. API Calls/Operations
10	10
100	100
1000	1000

Pattern observation: The operations increase in a straight line as resources increase.

Final Time Complexity

Time Complexity: O(n)

This means the cost optimization effort grows directly with the number of resources.

Common Mistake

[X] Wrong: "Cost optimization steps stay the same no matter how many resources we have."

[OK] Correct: Each resource needs its own review and action, so more resources mean more work.

Interview Connect

Understanding how cost optimization scales helps you plan and manage cloud budgets effectively in real projects.

Self-Check

"What if we automated cost optimization actions with AI? How would the time complexity change?"

Practice

1. Which AWS tool helps you understand and analyze your cloud spending over time?

easy

A. EC2 Dashboard

B. CloudTrail

C. Cost Explorer

D. IAM

Solution

1. Step 1: Identify AWS tools for cost management

   Cost Explorer is designed to analyze and visualize AWS spending over time.

2. Step 2: Compare other tools' purposes

   CloudTrail tracks API calls, EC2 Dashboard manages instances, IAM manages access, none focus on cost analysis.

3. Final Answer:

   Cost Explorer -> Option C

4. Quick Check:

   Cost analysis tool = Cost Explorer [OK]

Hint: Cost Explorer = spending analysis tool [OK]

Common Mistakes:

• Confusing CloudTrail with cost tool
• Thinking EC2 Dashboard shows costs
• Mixing IAM with billing

2. Which of the following is the correct AWS pricing option to save costs for steady-state workloads?

easy

A. On-Demand Instances

B. Reserved Instances

C. Spot Instances

D. Dedicated Hosts

Solution

1. Step 1: Understand pricing options

   Reserved Instances offer a discount for long-term, steady workloads by committing to usage.

2. Step 2: Compare other options

   On-Demand is pay-as-you-go, Spot is for interruptible workloads, Dedicated Hosts are costly physical servers.

3. Final Answer:

   Reserved Instances -> Option B

4. Quick Check:

   Steady workload savings = Reserved Instances [OK]

Hint: Reserved = save on steady workloads [OK]

Common Mistakes:

• Choosing On-Demand for savings
• Using Spot for steady workloads
• Confusing Dedicated Hosts with cost-saving

3. Consider this AWS Lambda function usage pattern: it runs 1000 times per day, each execution lasts 1 second, and uses 128 MB memory. Which change will reduce cost the most?

medium

A. Increase memory to 512 MB to reduce execution time

B. Decrease memory to 64 MB to save memory cost

C. Increase execution time to batch more work per run

D. Keep memory at 128 MB and reduce execution time by optimizing code

Solution

1. Step 1: Understand Lambda cost factors

   Cost depends on memory size and execution duration multiplied by invocations.

2. Step 2: Evaluate options

   Increasing memory may reduce time but might increase cost; decreasing memory may increase time; optimizing code reduces time without increasing memory.

3. Final Answer:

   Keep memory at 128 MB and reduce execution time by optimizing code -> Option D

4. Quick Check:

   Optimize code to reduce time = save cost [OK]

Hint: Lower execution time saves more than just lowering memory [OK]

Common Mistakes:

• Assuming more memory always saves cost
• Reducing memory without checking time
• Increasing execution time to batch

4. You notice your AWS Trusted Advisor reports underutilized EC2 instances. What is the best immediate action to optimize cost?

medium

A. Resize instances to smaller types matching usage

B. Terminate the underutilized instances immediately

C. Ignore the report as it might be inaccurate

D. Switch all instances to Dedicated Hosts

Solution

1. Step 1: Understand Trusted Advisor recommendations

   It flags underutilized instances to help reduce waste by resizing or terminating.

2. Step 2: Choose best cost optimization action

   Resizing to smaller instances keeps service running but reduces cost; terminating immediately may disrupt service; ignoring wastes money; Dedicated Hosts are expensive.

3. Final Answer:

   Resize instances to smaller types matching usage -> Option A

4. Quick Check:

   Resize underutilized = save cost safely [OK]

Hint: Resize before terminating to avoid downtime [OK]

Common Mistakes:

• Terminating without backup
• Ignoring Trusted Advisor
• Switching to costly Dedicated Hosts

5. A company wants to reduce AWS costs by automating resource scaling and tracking spending. Which combination of AWS services best supports this goal?

hard

A. AWS Auto Scaling + AWS Budgets + AWS Cost Explorer

B. AWS CloudTrail + AWS Config + AWS IAM

C. AWS Lambda + Amazon S3 + Amazon RDS

D. Amazon EC2 + AWS Trusted Advisor + AWS CloudWatch Logs

Solution

1. Step 1: Identify services for automated scaling

   AWS Auto Scaling automatically adjusts resource capacity based on demand.

2. Step 2: Identify services for cost tracking

   AWS Budgets sets spending limits and alerts; Cost Explorer analyzes spending patterns.

3. Step 3: Evaluate other options

   CloudTrail and Config track changes and security, not cost; Lambda, S3, RDS are compute/storage services; Trusted Advisor gives recommendations but not automation; CloudWatch Logs monitor logs.

4. Final Answer:

   AWS Auto Scaling + AWS Budgets + AWS Cost Explorer -> Option A

5. Quick Check:

   Auto scale + budgets + cost explorer = cost optimization [OK]

Hint: Auto Scaling + Budgets + Cost Explorer = automate cost control [OK]

Common Mistakes:

• Confusing CloudTrail with cost tools
• Choosing unrelated services
• Ignoring automation tools