Move note below cleanup

codetalkio · Oct 7, 2023 · 96e29e7 · 96e29e7
1 parent 295ba03
commit 96e29e7
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/posts/2023-10-07-the-stack-part-1.md b/posts/2023-10-07-the-stack-part-1.md
@@ -188,11 +188,6 @@ This ensures that both Config and CloudTrail can use the key for encryption and
 
 Review and confirm the setup.
 
-<div class="callout">
-  <div class="callout-bulb">💡</div>
-  If you missed the KMS policy adjustment in Step 4 and the creation fails, you can go into CloudFormation and delete the stack called `AWSControlTowerBP-BASELINE-CLOUDTRAIL-MASTER`. Once that is done, you can go back to the Control Tower console and click "Retry" to try again.
-</div>
-
 **Cleanup**
 
 Finally, we'll also cleanup the VPCs that were created in our Control Tower:
@@ -201,6 +196,11 @@ Finally, we'll also cleanup the VPCs that were created in our Control Tower:
 2. Click on **Your VPCs** in the menu on the left, and click on your Control Tower VPC.
 3. Choose **Actions** and then choose **Delete VPC** as well as confirming the choice.
 
+<div class="callout">
+  <div class="callout-bulb">💡</div>
+  If you missed the KMS policy adjustment in Step 4 and the creation fails, you can go into CloudFormation and delete the stack called `AWSControlTowerBP-BASELINE-CLOUDTRAIL-MASTER`. Once that is done, you can go back to the Control Tower console and click "Retry" to try again.
+</div>
+
 ## Adjusting Account Factory defaults
 
 By default the Account Factory will be creating VPCs and Subnets in newly provisioned accounts. We don't want this as we are focusing on serverless, so we'll disable this.