The following feed describes important changes in each release of the AWS CloudFormation User Guide after May 2018
You can iteratively develop your applications when provisioning failures are encountered by starting from the point of failure without rolling back successfully provisioned resources. By specifying stack failure options, you can troubleshoot resources in a CREATE_FAILED or UPDATE_FAILED status. You can provision failure options for all stack deployments and change Read more…
AWS KMS is replacing the term customer master key (CMK) with AWS KMS key and KMS key. The concept has not changed. To prevent breaking changes, AWS KMS is keeping some variations of this term.
The AWS CloudFormation stack import operation can import existing stacks into new or existing stack sets, so that you can migrate existing stacks to a stack set in one operation.
Use public extensions provided by third-party publishers, just as you would extensions from Amazon.
Fixed issues with the formatting and updated per China rebranding guidance.
In the NodegroupUpdateConfig, use either the MaxUnavailable and MaxUnavailablePercentage values to define the number of nodes to upgrade in parallel. In the scalingconfig, the minsize and desiredsize values can both be set to zero.
When using dynamic references, you can now have CloudFormation use the latest version of an SSM parameter whenever you create or update a stack. You are no longer required to specify a specific version.
StackSets now supports creating or updating stack sets with self-managed permissions from templates that reference macros. For more information about macros, see Using AWS CloudFormation macros to perform custom processing on templates.