prepare for release

Author: oliviergaumond

src/mkdocs/docs/lza-upgrade/faq.md

@@ -22,6 +22,9 @@ If this is not possible, you should record all route table information before th
 
 Note: Transit Gateway route tables are not replaced during the upgrade, theses guidelines only apply to subnet route tables.
 
+!!! tip
+    There is a script available to help detect drift on networking resources that are not detected by CloudFormation. The script is available in the [tools/network-drift-detection](https://github.com/aws-samples/aws-secure-environment-accelerator/tree/main/reference-artifacts/Custom-Scripts/lza-upgrade/tools/network-drift-detection/) folder in the ASEA to LZA upgrade tools.
+
 
 ## Gateway Load Balancer are not supported in the configuration conversion, how will this impact the workload availability?
 

src/mkdocs/docs/lza-upgrade/preparation/drift-handling.md

@@ -46,6 +46,9 @@ Pay special attention to drift on networking resources such as route tables and
 
 As an example, drift detection is not supported for resource type `AWS::EC2::SubnetRouteTableAssociation`. If you created route tables outside the accelerator and manually associated these route tables with an ASEA subnet, this change won't be detected in drift detection and the route table association will be reverted to the one defined in the configuration when installing LZA.
 
+!!! tip
+    There is a script available to help detect drift on networking resources that are not detected my CloudFormation. The script is available in the [tools/network-drift-detection](https://github.com/aws-samples/aws-secure-environment-accelerator/tree/main/reference-artifacts/Custom-Scripts/lza-upgrade/tools/network-drift-detection/) folder in the ASEA to LZA upgrade tools.
+
 !!! warning
     Remember that drift detection is a tool to help you identify manual changes done outside the accelerator, but it won't identify every change. Carefully review and analyze ALL changes done to accelerator resources outside of the configuration file.
 

src/mkdocs/docs/lza-upgrade/upgrade/disable-asea.md

@@ -6,22 +6,16 @@ To complete the upgrade process, we will need to disable ASEA Custom Resource de
 
 ### Deploy the upgrade ASEA Installer Stack
 
-- Navigate to the directory which contains the CloudFormation installer template:
-
-    ```bash
-    cd aws-secure-environment-accelerator
-    cd reference-artifacts/Custom-Scripts/lza-upgrade/cloudformation
-    ```
-
-  You will need to update the existing CloudFormation Installer stack:
+You will need to update the existing CloudFormation Installer stack:
 
+- Download the AcceleratorInstaller stack from the latest [ASEA Release](https://github.com/aws-samples/aws-secure-environment-accelerator/releases) on GitHub (i.e. v1.6.0 or later)
 - Navigate to the AWS CloudFormation console
 - Select the existing installer stack then **Update Stack**
 - On the **Update Stack** page, select the radio button for:
     - **Replace current template** under **Prepare Template Section**`
     - Click **Next**
     - **Upload a Template File** under **Specify Template Section**
-    - Select **Choose File** and navigate to the `cloudformation/AcceleratorInstaller.template.json` file.
+    - Select **Choose File** and navigate to the file downloaded from GitHub release page
     - Click **Next**
 - On the **Specify Stack Details** in the Parameters section update only the parameter named `LZAMigrationEnabled`. Change the value to `true`.
     - Update the parameter named `RepositoryBranch`. Change the value to the latest ASEA release (e.g. `release/v1.6.0`)