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 development team maintains the web application resources in a separate CloudFormation template.As the scope of the application grows, the software development team needs to use resources maintained by the database engineering team.However, both teams have their own review and lifecycle management processes that they want to keep.Both teams also require resource-level change-set reviews.The software development team would like to deploy changes to this template using their CI/CD pipeline.
Which solution will meet these requirements?
Create a stack export from the database CloudFormation template and import those references into the web application CloudFormation template.
Create a CloudFormation nested stack to make cross-stack resource references and parameters available in both stacks.
Create a CloudFormation stack set to make cross-stack resource references and parameters available in both stacks.
Create input parameters in the web application CloudFormation template and pass resource names and IDs from the database stack.
From my perspective, the answer is:
Create a stack export from the database CloudFormation template and import those references into the web application CloudFormation template.
I sort that the answer is:
Create a stack export from the database CloudFormation template and import those references into the web application CloudFormation template.