Creating stacks in AWS - Performance & Efficiency

Time Complexity: Creating stacks

O(n)

Understanding Time Complexity

When creating stacks in AWS, it is important to understand how the time to create resources grows as the number of resources increases.

We want to know how the total time or operations scale when we add more resources to a stack.

Scenario Under Consideration

Analyze the time complexity of creating an AWS CloudFormation stack with multiple resources.

aws cloudformation create-stack \
  --stack-name MyStack \
  --template-body file://template.yaml \
  --parameters ParameterKey=InstanceType,ParameterValue=t2.micro
    

This command creates a stack that provisions all resources defined in the template.

Identify Repeating Operations

When creating a stack, AWS performs these operations:

• Primary operation: Provisioning each resource defined in the template.
• How many times: Once per resource in the stack.

How Execution Grows With Input

As the number of resources in the template grows, the number of provisioning operations grows roughly the same way.

Input Size (n)	Approx. Api Calls/Operations
10	About 10 resource provisioning calls
100	About 100 resource provisioning calls
1000	About 1000 resource provisioning calls

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

Final Time Complexity

Time Complexity: O(n)

This means the time to create the stack grows linearly with the number of resources.

Common Mistake

[X] Wrong: "Creating a stack takes the same time no matter how many resources it has."

[OK] Correct: Each resource needs to be created, so more resources mean more work and more time.

Interview Connect

Understanding how resource count affects stack creation time helps you design efficient infrastructure and explain trade-offs clearly in interviews.

Self-Check

"What if the stack uses nested stacks? How would that affect the time complexity of creating the overall stack?"

Practice

1. What is the main purpose of creating a stack in AWS CloudFormation?

easy

A. To group related cloud resources for easy management

B. To write code for AWS Lambda functions

C. To monitor AWS billing and usage

D. To create user accounts in AWS IAM

Solution

1. Step 1: Understand what a stack represents

   A stack is a collection of AWS resources that you manage as a single unit.

2. Step 2: Identify the purpose of grouping resources

   Grouping resources simplifies deployment, updates, and deletion.

3. Final Answer:

   To group related cloud resources for easy management -> Option A

4. Quick Check:

   Stack = Group resources [OK]

Hint: Stacks group resources to manage them together [OK]

Common Mistakes:

• Confusing stacks with user accounts
• Thinking stacks are for billing
• Mixing stacks with Lambda code writing

2. Which AWS CLI command is used to create a stack from a template file named template.yaml?

easy

A. aws s3 create-bucket --template template.yaml

B. aws cloudformation create-stack --stack-name MyStack --template-body file://template.yaml

C. aws cloudformation deploy --stack-name MyStack --template-file file://template.yaml

D. aws ec2 create-stack --template-file template.yaml

Solution

1. Step 1: Identify the correct AWS service and command

   Creating stacks uses the AWS CloudFormation service and the command is create-stack.

2. Step 2: Check the correct syntax for template file input

   The template file is specified with --template-body file://filename.

3. Final Answer:

   aws cloudformation create-stack --stack-name MyStack --template-body file://template.yaml -> Option B

4. Quick Check:

   Use create-stack with --template-body file:// [OK]

Hint: Use create-stack with --template-body file:// [OK]

Common Mistakes:

• Using wrong AWS service like EC2 or S3
• Using --template-file instead of --template-body
• Confusing create-stack with deploy command

3. Given this AWS CLI command:
aws cloudformation create-stack --stack-name TestStack --template-body file://template.yaml --parameters ParameterKey=Env,ParameterValue=prod
What will happen when this command runs?

medium

A. The command will fail because parameters must be in JSON format

B. The stack will be created with default parameter values ignoring Env

C. The stack will be created but the Env parameter will be ignored

D. A stack named TestStack is created using the template with Env parameter set to prod

Solution

1. Step 1: Understand parameter usage in create-stack command

   The --parameters option allows passing key-value pairs to customize the stack.

2. Step 2: Check the syntax correctness

   The syntax ParameterKey=Env,ParameterValue=prod is valid for AWS CLI parameters.

3. Final Answer:

   A stack named TestStack is created using the template with Env parameter set to prod -> Option D

4. Quick Check:

   Parameters customize stack creation [OK]

Hint: Parameters use ParameterKey= and ParameterValue= pairs [OK]

Common Mistakes:

• Thinking parameters must be JSON
• Assuming parameters are ignored if passed
• Confusing parameter syntax with other commands

4. You run this command to create a stack:
aws cloudformation create-stack --stack-name MyStack --template-body file://template.yaml
But you get an error: Template format error: YAML not well-formed.
What is the most likely cause?

medium

A. The template.yaml file has syntax errors in YAML formatting

B. The stack name MyStack is invalid

C. The AWS CLI command is missing the region parameter

D. The template file path is incorrect

Solution

1. Step 1: Analyze the error message

   The error says "YAML not well-formed" which means the template file has syntax issues.

2. Step 2: Check other possible causes

   Stack name and region issues cause different errors; file path errors cause file not found errors.

3. Final Answer:

   The template.yaml file has syntax errors in YAML formatting -> Option A

4. Quick Check:

   YAML errors cause template format error [OK]

Hint: Check YAML syntax carefully for formatting errors [OK]

Common Mistakes:

• Assuming stack name causes YAML errors
• Ignoring file path correctness
• Forgetting to check template syntax

5. You want to create a stack that launches an EC2 instance with a parameter to choose the instance type. Your template uses a parameter named InstanceType. Which AWS CLI command correctly creates the stack with t3.micro as the instance type?

hard

A. aws cloudformation deploy --stack-name EC2Stack --template-file file://ec2.yaml --parameter-overrides InstanceType=t3.micro

B. aws cloudformation create-stack --stack-name EC2Stack --template-body file://ec2.yaml --parameters InstanceType=t3.micro

C. aws cloudformation create-stack --stack-name EC2Stack --template-body file://ec2.yaml --parameters ParameterKey=InstanceType,ParameterValue=t3.micro

D. aws ec2 run-instances --instance-type t3.micro --template-file ec2.yaml

Solution

1. Step 1: Identify the correct command and syntax for stack creation with parameters

   The create-stack command uses --parameters ParameterKey=key,ParameterValue=value syntax.

2. Step 2: Verify the parameter key and value match the template

   The parameter key is InstanceType and value is t3.micro, correctly formatted in aws cloudformation create-stack --stack-name EC2Stack --template-body file://ec2.yaml --parameters ParameterKey=InstanceType,ParameterValue=t3.micro.

3. Final Answer:

   aws cloudformation create-stack --stack-name EC2Stack --template-body file://ec2.yaml --parameters ParameterKey=InstanceType,ParameterValue=t3.micro -> Option C

4. Quick Check:

   Use ParameterKey= and ParameterValue= for parameters [OK]

Hint: Use ParameterKey= and ParameterValue= pairs for parameters [OK]

Common Mistakes:

• Using wrong parameter syntax
• Confusing deploy with create-stack
• Using EC2 CLI instead of CloudFormation