From 1c201170ced04b49199c177e045abf618fb68a24 Mon Sep 17 00:00:00 2001 From: Brian969 <56414362+Brian969@users.noreply.github.com> Date: Sun, 17 Jul 2022 14:07:43 -0400 Subject: [PATCH] (doc)tweaks for153 (#1018) --- src/mkdocs/docs/installation/install.md | 4 ++-- src/mkdocs/docs/installation/upgrades.md | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/mkdocs/docs/installation/install.md b/src/mkdocs/docs/installation/install.md index 557072b24..0d10508bb 100644 --- a/src/mkdocs/docs/installation/install.md +++ b/src/mkdocs/docs/installation/install.md @@ -213,7 +213,7 @@ Multiple options exist for downloading the GitHub Accelerator codebase and pushi - Do NOT download the code off the main GitHub branch, this will leave you in a completely unsupported state (and with beta code) 3. Push the extracted codebase into the newly created CodeCommit repository, maintaining the file/folder hierarchy 4. Set the default CodeCommit branch for the new repository to main -5. Create a branch following the Accelerator naming format for your release (i.e. `release/v1.5.2`) +5. Create a branch following the Accelerator naming format for your release (i.e. `release/v1.5.3`) ### 1.4.3. AWS Internal (Employee) Accounts Only @@ -316,7 +316,7 @@ If deploying to an internal AWS employee account and installing the solution wit - Add an `Email` address to be used for State Machine Status notification - The `GitHub Branch` should point to the release you selected - if upgrading, change it to point to the desired release - - the latest stable branch is currently `release/v1.5.2`, case sensitive + - the latest stable branch is currently `release/v1.5.3`, case sensitive - click `Next` 7. Finish deploying the stack - Apply a tag on the stack, Key=`Accelerator`, Value=`ASEA` (case sensitive). diff --git a/src/mkdocs/docs/installation/upgrades.md b/src/mkdocs/docs/installation/upgrades.md index c50f4a93a..858e7099e 100644 --- a/src/mkdocs/docs/installation/upgrades.md +++ b/src/mkdocs/docs/installation/upgrades.md @@ -17,11 +17,11 @@ ## 1.2. **Release Specific Upgrade Considerations:** -- Upgrades to `v1.5.1-a` from `v1.5.0` or `v1.5.1`: +- Upgrades to `v1.5.1-a and above` from `v1.5.0` or `v1.5.1`: - Do not add the parameter: `"ssm-inventory-collection": true` to OUs or accounts which already have SSM Inventory configured or the state machine will fail - Follow the standard upgrade steps detailed in section 3.2 below -- v1.5.1 was replaced by v1.5.1-a and is no longer supported for new installs or upgrades -- Upgrades to `v1.5.0` and `v1.5.1-a` from `v1.3.8 through v1.3.9`: +- `v1.5.1` was replaced by v1.5.1-a and is no longer supported for new installs or upgrades +- Upgrades to `v1.5.0` and `v1.5.1-a and above` from `v1.3.8 through v1.3.9`: - We recommend upgrading directly to v1.5.1-a - Due to the size and complexity of this upgrade, we require all customers to upgrade to `v1.3.8 or above` before beginning this upgrade - While v1.5.0 supports Control Tower for _NEW_ installs, existing Accelerator customers _CANNOT_ add Control Tower to their existing installations at this time (planned enhancement for 22H1)