Outputs for cross-stack references in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to export a value from a CloudFormation stack output.

AWS

Outputs:
  MyBucketName:
    Value: !Ref MyBucket
    Export:
      Name: [1]

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

AMyBucketNameExport

BBucketNameExport

CMyBucketName

DExportedBucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using a name that does not match the output logical name.

Leaving the export name empty.

The export name must be a unique string used to reference this output in other stacks. Here, using the output logical name MyBucketName as the export name is a common practice.

2fill in blank

medium

Complete the code to import an exported value from another CloudFormation stack.

AWS

Resources:
  MyBucketPolicy:
    Type: AWS::S3::BucketPolicy
    Properties:
      Bucket: !ImportValue [1]

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

AExportedBucket

BOtherStack-MyBucketName

CMyBucketNameExport

DMyBucketName

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different or incorrect export name.

Confusing the logical resource name with the export name.

The !ImportValue function requires the exact export name defined in the other stack's outputs. Here, it matches the export name MyBucketName.

3fill in blank

hard

Fix the error in the output export name to make it valid for cross-stack reference.

AWS

Outputs:
  MyBucketArn:
    Value: !GetAtt MyBucket.Arn
    Export:
      Name: [1]

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

AMy Bucket Arn

BMyBucket_Arn

CMyBucketArn!

DMyBucketArn

Attempts:

3 left

💡 Hint

Common Mistakes

Including spaces in export names.

Using special characters like exclamation marks.

Export names must be alphanumeric or include hyphens and underscores but cannot contain spaces or special characters like exclamation marks. MyBucket_Arn is valid.

4fill in blank

hard

Fill both blanks to correctly export and import a VPC ID between stacks.

AWS

Outputs:
  VPCId:
    Value: !Ref MyVPC
    Export:
      Name: [1]

Resources:
  MySubnet:
    Type: AWS::EC2::Subnet
    Properties:
      VpcId: !ImportValue [2]

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

AMyApp-VPC

BMyApp_VPC

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatch between export and import names.

Using spaces or invalid characters.

The export and import names must match exactly. Here, the export name is MyApp-VPC and the import uses the same string.

5fill in blank

hard

Fill all three blanks to export an RDS instance endpoint and import it in another stack.

AWS

Outputs:
  DBEndpoint:
    Value: !GetAtt MyDB.Endpoint.Address
    Export:
      Name: [1]

Resources:
  MyAppDBConnection:
    Type: AWS::RDS::DBInstance
    Properties:
      DBInstanceIdentifier: mydb
      EndpointAddress: !ImportValue [2]
      Port: [3]

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

AMyApp-DBEndpoint

C3306

D5432

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatched export/import names.

Using the wrong port number for the database.

The export and import names must match exactly (MyApp-DBEndpoint). The port 3306 is the default for MySQL RDS instances.

Practice

1. What is the main purpose of using Outputs in AWS CloudFormation stacks?

easy

A. To share important values like resource IDs between different stacks

B. To delete resources automatically after stack deletion

C. To increase the stack creation speed

D. To encrypt stack resources

Solution

1. Step 1: Understand Outputs role

   Outputs provide a way to expose key information from one stack.

2. Step 2: Identify sharing purpose

   This information can be used by other stacks to reference resources like IDs or names.

3. Final Answer:

   To share important values like resource IDs between different stacks -> Option A

4. Quick Check:

   Outputs share values across stacks = A [OK]

Hint: Outputs share values between stacks, not speed or encryption [OK]

Common Mistakes:

• Thinking Outputs delete resources
• Believing Outputs speed up stack creation
• Confusing Outputs with encryption

2. Which syntax correctly exports an output value named MyBucketName for cross-stack use in CloudFormation?

easy

A. "Outputs": { "BucketName": { "Value": "MyBucket", "Export": "MyBucketName" } }

B. "Outputs": { "BucketName": { "Value": { "Ref": "MyBucket" }, "ExportName": "MyBucketName" } }

C. "Outputs": { "BucketName": { "Value": { "Ref": "MyBucket" }, "Export": { "Name": "MyBucketName" } } }

D. "Outputs": { "BucketName": { "Value": { "GetAtt": ["MyBucket", "Name"] }, "Export": { "Name": "MyBucketName" } } }

Solution

1. Step 1: Check correct Export syntax

   The Export field must be an object with a Name key inside Outputs.

2. Step 2: Validate Ref usage and Export name

   "Outputs": { "BucketName": { "Value": { "Ref": "MyBucket" }, "Export": { "Name": "MyBucketName" } } } uses correct Ref and Export with Name key, matching CloudFormation syntax.

3. Final Answer:

   "Outputs": { "BucketName": { "Value": { "Ref": "MyBucket" }, "Export": { "Name": "MyBucketName" } } } -> Option C

4. Quick Check:

   Export uses Export: { Name: "..." } = A [OK]

Hint: Export must be an object with Name key, not a string [OK]

Common Mistakes:

• Using ExportName instead of Export with Name
• Setting Export as a string instead of object
• Incorrect Value reference syntax

3. Given two stacks, StackA exports an output named VpcId. StackB imports it using Fn::ImportValue. What will happen if StackA's export name changes but StackB is not updated?

medium

A. StackB will ignore the import and deploy without errors

B. StackB will automatically update to the new export name

C. StackB will use the old value cached locally

D. StackB deployment will fail because the import value no longer exists

Solution

1. Step 1: Understand ImportValue dependency

   StackB depends on StackA's export name to import the value correctly.

2. Step 2: Effect of changing export name

   If StackA changes the export name, StackB's import reference breaks and causes deployment failure.

3. Final Answer:

   StackB deployment will fail because the import value no longer exists -> Option D

4. Quick Check:

   ImportValue depends on exact export name = D [OK]

Hint: ImportValue needs exact export name; changes break import [OK]

Common Mistakes:

• Assuming imports auto-update with export name changes
• Believing imports cache old values
• Thinking imports are optional and ignored if missing

4. You have this output in StackA:

{
  "Outputs": {
    "SubnetId": {
      "Value": { "Ref": "Subnet" },
      "Export": { "Name": "SubnetId" }
    }
  }
}

When deploying StackB that imports SubnetId, you get an error about duplicate export names. What is the likely cause?

medium

A. StackB is missing the ImportValue function

B. Another stack already exports the name "SubnetId", causing a conflict

C. The export name "SubnetId" is invalid and not allowed

D. The Ref function is used incorrectly in the output

Solution

1. Step 1: Understand export name uniqueness

   Export names must be unique across all stacks in the same region and account.

2. Step 2: Identify cause of duplicate export error

   The error means another stack already uses "SubnetId" as an export name, causing conflict.

3. Final Answer:

   Another stack already exports the name "SubnetId", causing a conflict -> Option B

4. Quick Check:

   Export names must be unique = C [OK]

Hint: Export names must be unique across stacks to avoid conflicts [OK]

Common Mistakes:

• Thinking export names can be reused in different stacks
• Assuming ImportValue missing causes export conflict
• Believing Ref usage causes export name errors

5. You want to share a VPC ID from StackA to StackB using outputs and imports. StackA exports the VPC ID as VpcIdExport. StackB imports it with Fn::ImportValue: VpcIdExport. Later, you need to update StackA to create a new VPC and export its ID with the same name. What is the best practice to avoid deployment failures in StackB?

hard

A. Change the export name in StackA and update StackB to import the new name

B. Delete StackB before updating StackA, then redeploy StackB after update

C. Keep the export name the same and update StackB without changes

D. Remove the export from StackA and hardcode the VPC ID in StackB

Solution

1. Step 1: Recognize export name immutability

   Export names cannot be changed or deleted without affecting dependent stacks.

2. Step 2: Plan safe update

   To update the VPC and export a new ID, use a new export name and update StackB to import that new name.

3. Step 3: Avoid breaking dependencies

   This avoids deployment failures and keeps stacks consistent.

4. Final Answer:

   Change the export name in StackA and update StackB to import the new name -> Option A

5. Quick Check:

   Update export name and import to avoid conflicts = B [OK]

Hint: Change export name and update imports to avoid breaking stacks [OK]

Common Mistakes:

• Deleting dependent stacks before update
• Keeping export name same causing conflicts
• Hardcoding values instead of using imports