From 62eb6bb857f258478e90683453387e19bd80e716 Mon Sep 17 00:00:00 2001 From: Julien Duchesne Date: Thu, 31 Aug 2017 20:11:20 -0400 Subject: [PATCH 1/2] Fixed incorrect statement about failed cloudformation update recovery --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index fa6e371..1c4396c 100644 --- a/README.md +++ b/README.md @@ -1455,7 +1455,7 @@ CloudFormation ### CloudFormation Gotchas and Limitations -- ❗Modifications to stack resources made outside CloudFormation can potentially lead to stacks stuck in UPDATE\_ROLLBACK\_FAILED mode. Stacks in this state can‘t be recovered without help from AWS Support. +- ❗Modifications to stack resources made outside CloudFormation can potentially lead to stacks stuck in UPDATE\_ROLLBACK\_FAILED mode. Stacks in this state can be recovered using the [continue-update-rollback command](https://aws.amazon.com/blogs/devops/continue-rolling-back-an-update-for-aws-cloudformation-stacks-in-the-update_rollback_failed-state/). This command can be initiated in the console or in the CLI. The [--resources-to-skip](http://docs.aws.amazon.com/cli/latest/reference/cloudformation/continue-update-rollback.html ) parameter usable in the CLI can be useful if the continue-update-rollback command fails. - 🔸CloudFormation is useful but complex and with a variety of pain points. Many companies find alternate solutions, and many companies use it, but only with significant additional tooling. - 🔸CloudFormation can be very slow, especially for items like CloudFront distributions and Route53 CNAME entries. - 🔸It’s hard to assemble good CloudFormation configurations from existing state. AWS does [offer a trick to do this](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-using-cloudformer.html), but it’s very clumsy. From 1a111194c6cdb55e06b3d7c2629836d7a923c7f6 Mon Sep 17 00:00:00 2001 From: Julien Duchesne Date: Fri, 1 Sep 2017 07:28:25 -0400 Subject: [PATCH 2/2] Removed unneeded whitespace in Cloudformation tip --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1c4396c..c50de49 100644 --- a/README.md +++ b/README.md @@ -1455,7 +1455,7 @@ CloudFormation ### CloudFormation Gotchas and Limitations -- ❗Modifications to stack resources made outside CloudFormation can potentially lead to stacks stuck in UPDATE\_ROLLBACK\_FAILED mode. Stacks in this state can be recovered using the [continue-update-rollback command](https://aws.amazon.com/blogs/devops/continue-rolling-back-an-update-for-aws-cloudformation-stacks-in-the-update_rollback_failed-state/). This command can be initiated in the console or in the CLI. The [--resources-to-skip](http://docs.aws.amazon.com/cli/latest/reference/cloudformation/continue-update-rollback.html ) parameter usable in the CLI can be useful if the continue-update-rollback command fails. +- ❗Modifications to stack resources made outside CloudFormation can potentially lead to stacks stuck in UPDATE\_ROLLBACK\_FAILED mode. Stacks in this state can be recovered using the [continue-update-rollback command](https://aws.amazon.com/blogs/devops/continue-rolling-back-an-update-for-aws-cloudformation-stacks-in-the-update_rollback_failed-state/). This command can be initiated in the console or in the CLI. The [--resources-to-skip](http://docs.aws.amazon.com/cli/latest/reference/cloudformation/continue-update-rollback.html) parameter usable in the CLI can be useful if the continue-update-rollback command fails. - 🔸CloudFormation is useful but complex and with a variety of pain points. Many companies find alternate solutions, and many companies use it, but only with significant additional tooling. - 🔸CloudFormation can be very slow, especially for items like CloudFront distributions and Route53 CNAME entries. - 🔸It’s hard to assemble good CloudFormation configurations from existing state. AWS does [offer a trick to do this](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-using-cloudformer.html), but it’s very clumsy.