A company is developing a web application's infrastructure using AWS CloudFormation. The database engineering team maintains the database resources in a CloudFormation template, and the software devel

Creating a stack export from the database CloudFormation template and importing those values into the web application template provides loose coupling, allowing each team to maintain independent review and lifecycle processes while enabling cross-stack resource referencing.

Using CloudFormation nested stacks creates a tight coupling where the parent stack manages the lifecycle of the child stack, thus violating the requirement for separate review and lifecycle management processes for each team.

CloudFormation StackSets are designed for deploying the same stack across multiple accounts or regions, not for managing dependencies or sharing resources between different stacks within a single application in one account.

Creating input parameters and manually passing resource references is error-prone and does not provide an automated, robust mechanism for cross-stack referencing that adapts to changes in the database stack outputs.