3 ms·

The CloudFormation one is pretty accurate. Relying on nested stacks to "share" templating pieces: never again.

• gonzo41 6y ago
  And that's exactly the feeling I had, but hey we're in prod now, so we'll circle back in 5 years to see what we do next.
  • mattacular 6y ago
    Don't fret! You still have to look forward to all the weird service limits you'll hit both directly and indirectly using CFN to maintain and extend a prod infrastructure YoY
• mvanbaak 6y ago
  One can use AWS::Include. See https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/create-reusable-transform-function-snippets-and-add-to-your-template-with-aws-include-transform.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...
• synthc 6y ago
  Nested stacks are a pain: use imports and exports and keep your stacks small to lessen the pain.