Skip to content

Commit

Permalink
(doc)tweaks for153 (#1018)
Browse files Browse the repository at this point in the history
Brian969 authored Jul 17, 2022

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
1 parent 3c5a799 commit 1c20117
Showing 2 changed files with 5 additions and 5 deletions.
4 changes: 2 additions & 2 deletions src/mkdocs/docs/installation/install.md
Original file line number Diff line number Diff line change
@@ -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).
6 changes: 3 additions & 3 deletions src/mkdocs/docs/installation/upgrades.md
Original file line number Diff line number Diff line change
@@ -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)

0 comments on commit 1c20117

Please sign in to comment.