Question

A SysOps administrator is building a CloudFormation architecture for a multi-tier application. A parent stack must provision a shared VPC and subnets, and several child stacks (application, database, and cache tiers) must reference the VPC ID and subnet IDs created by the networking layer. The administrator wants the tiers deployed and managed as a single deployable unit, so that updating or deleting the parent stack automatically manages all tiers together. Which approach meets these requirements?

Accepted Answer

Use nested stacks by defining AWS::CloudFormation::Stack resources in the parent template, passing the VPC and subnet IDs to each child stack via Parameters

Answer

Deploy each tier as an independent stack and share the VPC ID and subnet IDs using cross-stack references with Export and Fn::ImportValue

Answer

Deploy each tier as an independent stack and store the VPC ID and subnet IDs in SSM Parameter Store, then resolve them in each template with dynamic references

Answer

Use a StackSet to deploy the networking and application templates to multiple accounts so they share the same VPC resources