1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Hi,
You have a simpler optiony breaking your big template into a set of smaller templates (each stored as SSM document) and share the info that you need via outputs that you export into a namespace that you define. Then you read those exported values from your other templates that need those values.
Re. exports, see https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/outputs-section-structure.html
The optimal way is to organize your new templates by "layers" of resources corresponding to the dependencies between all of them.
That is what I personally use very often in similar situations.
Best,
Didier
関連するコンテンツ
AWS公式更新しました 2年前
Thanks for the suggestion!
We already have "layered" templates using export/import as well as SSM Parameters. However, the initial template is fairly large because it is the only one that requires IAM capability during create/update (very important for the delegation of permissions).
If we did break this template into smaller templates, we would need to perform multiple "Create Application" operations in Application Manager (or Cfn UI / CLI) for the same end result. Seems unfortunate but storing templates in SSM Documents brings important value.
Thanks, Thomas Å.