Hi, This very recent blog post details how to coordinate complex resource dependencies across CloudFormation stacks.

https://aws.amazon.com/blogs/mt/coordinating-complex-resource-dependencies-across-cloudformation-stacks/

It looks like what you want to achieve.

Best,

Didier

Absolutely, you can achieve a cleaner and more organized AWS Cloud Formation template structure by splitting your stack resources into separate files and including them without resorting to nested stacks. This approach is highly beneficial for managing large-scale templates with numerous resources. Here's how you can accomplish this using YAML:

MainTemplate.yaml: In your main template, you can use the Resources section to include the resources from separate files using the AWS::Include transform. Here's an example: AWSTemplateFormatVersion: '2010-09-09' Transform: 'AWS::Include' Resources: Resource1: Type: 'AWS::CloudFormation::Include' Properties: Location: Resource1.yaml Resource2: Type: 'AWS::CloudFormation::Include' Properties: Location: Resource2.yaml

... continue for other resources

Absolutely, you can achieve a cleaner and more organized AWS CloudFormation template structure by splitting your stack resources into separate files and including them without resorting to nested stacks. This approach is highly beneficial for managing large-scale templates with numerous resources. Here's how you can accomplish this using YAML:

MainTemplate.yaml: In your main template, you can use the Resources section to include the resources from separate files using the AWS::Include transform. Here's an example: yaml Copy code AWSTemplateFormatVersion: '2010-09-09' Transform: 'AWS::Include' Resources: Resource1: Type: 'AWS::CloudFormation::Include' Properties: Location: Resource1.yaml Resource2: Type: 'AWS::CloudFormation::Include' Properties: Location: Resource2.yaml

... continue for other resources

Resource5.yaml: In your Resource5.yaml file, you can include sub-resources using the same technique. For instance: AWSTemplateFormatVersion: '2010-09-09' Transform: 'AWS::Include' Resources: Resource5: Type: 'AWS::CloudFormation::Include' Properties: Location: Sub1Resource5.yaml

... include other sub-resources similarly

Sharing Parameters and Resources: You can define shared parameters and resources in a separate file, let's call it CommonResources.yaml, and then include it in your individual resource files. For example: AWSTemplateFormatVersion: '2010-09-09' Parameters: SharedParameter: Type: String Default: SharedParameterValue

Resources: SharedResource: Type: AWS::SomeResourceType Properties: # Properties of the shared resource In Resource1.yaml: AWSTemplateFormatVersion: '2010-09-09' Transform: 'AWS::Include' Resources: Resource1: Type: 'AWS::CloudFormation::Include' Properties: Location: CommonResources.yaml This approach maintains clarity, modularity, and reusabilityhttps://proracketreviews.com/making your CloudFormation template significantly more manageable. It also allows you to maintain a consistent structure across different files while sharing parameters and resources effectively.

Hope this helps! If you have any further questions, feel free to ask.