Separate network, monitoring, and application resources into different CloudFormation stacks.
Let the application stack use the shared VPC while keeping update boundaries separate.
Which design is most appropriate?
Use nested stacks and stack Outputs to pass shared resource values between the parent and child stacks.
Detailed explanation
A DNS record does not share CloudFormation output values.
A DNS record does not share CloudFormation output values.
A parent stack manages child stacks, and output values pass resource identifiers between them.
A parent stack manages child stacks, and output values pass resource identifiers between them.
An object name is not a CloudFormation resource reference.
An object name is not a CloudFormation resource reference.
Duplicating the VPC creates needless resources and configuration drift.
Duplicating the VPC creates needless resources and configuration drift.
Check official documentation
Compare the following points with the official documentation.
CloudFormation nested stacks and outputsの公式説明を確認する。
What to confirm
スタック分割と手動複製の違いを説明できる。
Key points
- Nested stack
- CloudFormation Outputs
- Stack separation
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Composition
Nested stacks let a larger deployment compose reusable infrastructure units.
Value passing
Outputs pass identifiers without recreating the shared resource.