The following feed describes important changes in each release of the AWS CloudFormation User Guide after May 2018
AWS CloudFormation announces the general availability of hooks, a feature that allows customers to invoke custom logic to automate actions or inspect resource configurations prior to a create, update or delete stack operation.
The following properties were added under AWS::ApplicationInsights::Application.ConfigurationDetails:
For the AWS::Chatbot::SlackChannelConfiguration resource, the GuardrailPolicies property was updated and the UserRoleRequired property was added.
You can activate managed execution for your stack set so that StackSets performs non-conflicting operations concurrently and queues conflicting operations. After conflicting operations finish, StackSets starts queued operations in request order.
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.
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…
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.