E.g. the following issues can be addressed via resp. template patterns now (by converting semantically optional parameters to actually optional ones):
optional EBS snapshot submissions (i.e. create a new volume if snapshot id is absent)
optional EC2 spot instance usage (i.e. create an on demand instance if spot price is 0)
optional SNS notifications (i.e. omit Auto Scaling notifications if no ARN is supplied
Also worth noting, though not relevant yet:
optional IOPS specification
optional VPC support (i.e. work around the inconsistent id vs. name reference requirements - untested, but should work likewise, albeit a bit more convoluted template wise)
dpb587
commented
10 years ago
The New Stack Management and Template Features in AWS CloudFormation in general (as mentioned in https://github.com/cityindex/logsearch/issues/238#issuecomment-29598840 already) and the Conditions Declaration and Condition Functions in particular turn out to be much more powerful than I realized at first sight, thereby providing options to address a variety of limitations and annoyances of CloudFormation we encountered over time.
E.g. the following issues can be addressed via resp. template patterns now (by converting semantically optional parameters to actually optional ones):
Also worth noting, though not relevant yet: