A database team maintains database resources in one CloudFormation template and a software team maintains web application resources in another template. The software team needs to reference database resources while keeping separate review/lifecycle processes and resource-level change-set reviews. The software team will deploy changes from its own CI/CD pipeline. What solution satisfies these requirements?

Exporting outputs from the database CloudFormation template and importing them into the web application template allows the software team to reference database resources without directly managing the database stack. This maintains separate review and lifecycle processes for each team and enables resource-level change-set reviews for the web application template independently. The software team can deploy changes from its own CI/CD pipeline using these imported values. Using a nested stack would couple the lifecycles and review processes, which is not desired. CloudFormation StackSets are for deploying common stacks across multiple accounts and regions, not for cross-stack resource referencing within the same account and region for independent teams. Passing parameters manually would require the software team to know and update database resource identifiers, making the process less automated and prone to errors, and not providing the desired separation of concerns.