Nested stacks for modularity in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a nested stack resource in AWS CloudFormation.

AWS

Resources:
  NestedStack:
    Type: [1]
    Properties:
      TemplateURL: https://s3.amazonaws.com/mybucket/mytemplate.yaml

Drag options to blanks, or click blank then click option'

AAWS::S3::Bucket

BAWS::CloudFormation::Stack

CAWS::EC2::Instance

DAWS::Lambda::Function

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource types like AWS::S3::Bucket instead of AWS::CloudFormation::Stack.

Confusing nested stack with other AWS resources.

The nested stack resource type in CloudFormation is AWS::CloudFormation::Stack. This allows you to include another template inside your main template.

2fill in blank

medium

Complete the code to pass a parameter named 'EnvType' to the nested stack.

AWS

Resources:
  NestedStack:
    Type: AWS::CloudFormation::Stack
    Properties:
      TemplateURL: https://s3.amazonaws.com/mybucket/mytemplate.yaml
      Parameters:
        EnvType: [1]

Drag options to blanks, or click blank then click option'

AProduction

B"Production"

CEnvType

D!Ref EnvType

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a plain string without quotes or intrinsic functions.

Using the parameter name as a string instead of referencing it.

To pass a parameter from the parent stack to the nested stack, you use !Ref EnvType to reference the parameter value defined in the parent stack.

3fill in blank

hard

Fix the error in the nested stack resource by completing the missing property key.

AWS

Resources:
  NestedStack:
    Type: AWS::CloudFormation::Stack
    Properties:
      [1]: https://s3.amazonaws.com/mybucket/mytemplate.yaml

Drag options to blanks, or click blank then click option'

ATemplateBody

BTemplatePath

CTemplateURL

DTemplateFile

Attempts:

3 left

💡 Hint

Common Mistakes

Using TemplateBody instead of TemplateURL for external templates.

Using incorrect property names like TemplatePath or TemplateFile.

The correct property to specify the location of the nested stack template is TemplateURL. It must be a URL to the template file in S3 or another accessible location.

4fill in blank

hard

Fill both blanks to define outputs in the nested stack and reference them in the parent stack.

AWS

Resources:
  NestedStack:
    Type: AWS::CloudFormation::Stack
    Properties:
      TemplateURL: https://s3.amazonaws.com/mybucket/mytemplate.yaml
Outputs:
  NestedOutputValue:
    Value: ![1] NestedStack.[2]

Drag options to blanks, or click blank then click option'

AGetAtt

BRef

COutputs

DAttributes

Attempts:

3 left

💡 Hint

Common Mistakes

Using !Ref instead of !GetAtt to access nested stack outputs.

Using wrong keys like Attributes instead of Outputs.

To get an output value from a nested stack, you use !GetAtt NestedStack.Outputs.OutputName. Here, Outputs is the key to access the nested stack's outputs.

5fill in blank

hard

Fill all three blanks to pass multiple parameters and set the timeout for the nested stack.

AWS

Resources:
  NestedStack:
    Type: AWS::CloudFormation::Stack
    Properties:
      TemplateURL: https://s3.amazonaws.com/mybucket/mytemplate.yaml
      Parameters:
        EnvType: [1]
        InstanceType: [2]
      [3]: 30

Drag options to blanks, or click blank then click option'

A!Ref EnvType

B!Ref InstanceType

CTimeoutInMinutes

DTimeout

Attempts:

3 left

💡 Hint

Common Mistakes

Using plain strings instead of !Ref for parameters.

Using incorrect timeout property names like Timeout.

To pass parameters, use !Ref to reference parent stack parameters. The timeout property for nested stacks is TimeoutInMinutes.

Practice

1. What is the main benefit of using nested stacks in AWS CloudFormation?

easy

A. They replace the need for IAM roles.

B. They automatically increase server CPU capacity.

C. They break large templates into smaller, reusable parts.

D. They encrypt all data stored in S3 buckets.

Solution

1. Step 1: Understand the purpose of nested stacks

   Nested stacks allow splitting a big CloudFormation template into smaller templates for easier management.

2. Step 2: Compare options with this purpose

   Only They break large templates into smaller, reusable parts. describes breaking large templates into reusable parts, which matches nested stacks' main benefit.

3. Final Answer:

   They break large templates into smaller, reusable parts. -> Option C

4. Quick Check:

   Nested stacks = modular templates [OK]

Hint: Think modular: nested stacks split big templates [OK]

Common Mistakes:

• Confusing nested stacks with scaling features
• Assuming nested stacks handle encryption automatically
• Mixing nested stacks with IAM role functions

2. Which syntax correctly defines a nested stack resource in a CloudFormation template?

easy

A. "Type": "AWS::Lambda::Function",
"Properties": {"Handler": "index.handler"}

B. "Type": "AWS::S3::Bucket",
"Properties": {"BucketName": "nested-stack"}

C. "Type": "AWS::EC2::Instance",
"Properties": {"ImageId": "ami-123456"}

D. "Type": "AWS::CloudFormation::Stack",
"Properties": {"TemplateURL": "https://s3.amazonaws.com/mybucket/mystack.yaml"}

Solution

1. Step 1: Identify nested stack resource type

   The resource type for nested stacks is AWS::CloudFormation::Stack.

2. Step 2: Check the properties for nested stack

   Nested stacks require a TemplateURL property pointing to the child template location.

3. Final Answer:

   "Type": "AWS::CloudFormation::Stack", "Properties": {"TemplateURL": "https://s3.amazonaws.com/mybucket/mystack.yaml"} -> Option D

4. Quick Check:

   Nested stack resource = AWS::CloudFormation::Stack [OK]

Hint: Nested stack resource type is AWS::CloudFormation::Stack [OK]

Common Mistakes:

• Using S3 bucket or EC2 instance types for nested stacks
• Omitting TemplateURL property
• Confusing Lambda function syntax with nested stacks

3. Given a parent stack that passes a parameter VpcId to a nested stack, what will happen if the nested stack template does NOT declare VpcId as a parameter?

medium

A. The nested stack deployment will fail with a parameter validation error.

B. The nested stack will ignore the parameter and deploy successfully.

C. The parent stack will automatically create the missing parameter.

D. The nested stack will use a default VPC ID automatically.

Solution

1. Step 1: Understand parameter passing in nested stacks

   Parameters passed from parent to nested stack must be declared in the nested stack template.

2. Step 2: Consequence of missing parameter declaration

   If the nested stack does not declare the parameter, CloudFormation cannot map the value, causing deployment failure.

3. Final Answer:

   The nested stack deployment will fail with a parameter validation error. -> Option A

4. Quick Check:

   Missing nested stack parameter = deployment error [OK]

Hint: Nested stack must declare all passed parameters [OK]

Common Mistakes:

• Assuming parameters are optional in nested stacks
• Thinking parent stack auto-creates missing parameters
• Believing nested stacks use default values without declaration

4. You have a nested stack that fails to update because the child stack template URL is incorrect. What is the best way to fix this error?

medium

A. Delete the parent stack and recreate it from scratch.

B. Update the parent stack template to use the correct TemplateURL for the nested stack.

C. Change the nested stack resource type to AWS::S3::Bucket.

D. Remove the nested stack resource from the parent template.

Solution

1. Step 1: Identify cause of failure

   The error is due to an incorrect TemplateURL in the parent stack referencing the nested stack template.

2. Step 2: Correct the TemplateURL

   Fixing the TemplateURL in the parent stack template ensures CloudFormation can find and deploy the nested stack correctly.

3. Final Answer:

   Update the parent stack template to use the correct TemplateURL for the nested stack. -> Option B

4. Quick Check:

   Fix TemplateURL in parent stack to fix nested stack update [OK]

Hint: Fix TemplateURL in parent template to fix nested stack errors [OK]

Common Mistakes:

• Deleting entire parent stack unnecessarily
• Changing resource type incorrectly
• Removing nested stack resource instead of fixing URL

5. You want to create a modular infrastructure with nested stacks where a VPC stack outputs a VpcId and a subnet stack needs this VpcId as input. How should you connect these stacks to ensure modularity and correct parameter passing?

hard

A. Use Outputs in the VPC stack and pass them as Parameters to the subnet nested stack in the parent template.

B. Hardcode the VPC ID in the subnet stack template directly.

C. Deploy the subnet stack separately without any parameters.

D. Merge both VPC and subnet resources into a single large template.

Solution

1. Step 1: Use Outputs to share data from VPC stack

   The VPC nested stack should declare an Output for VpcId to share it externally.

2. Step 2: Pass Output as Parameter to subnet stack

   The parent stack template passes the VPC stack's VpcId Output as a Parameter to the subnet nested stack, maintaining modularity.

3. Final Answer:

   Use Outputs in the VPC stack and pass them as Parameters to the subnet nested stack in the parent template. -> Option A

4. Quick Check:

   Outputs to Parameters connect nested stacks modularly [OK]

Hint: Connect stacks via Outputs and Parameters in parent template [OK]

Common Mistakes:

• Hardcoding values breaking modularity
• Deploying stacks separately without parameter passing
• Combining all resources in one big template losing modularity