Skip to content

Commit 24dc6b0

Browse files
add doc to use installer stack for a specific version
1 parent 9d4702c commit 24dc6b0

File tree

1 file changed

+17
-4
lines changed
  • src/mkdocs/docs/lza-upgrade

1 file changed

+17
-4
lines changed

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

Lines changed: 17 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -90,9 +90,22 @@ For more information about LZA related Quotas, refer to the [LZA Documentation a
9090

9191
By default, the LZA upgrade tools install the latest LZA official release. To specify a version to use, follow these instructions:
9292

93-
1. Run `yarn migration-config` from the [Preparation phase](./preparation/prereq-config/#configuration)
93+
1. Run `yarn migration-config` from the [Preparation phase](./preparation/prereq-config.md#configuration)
9494
2. Edit the `src/input-config/input-config.json` file
95-
3. Add the following property to the file to specify which branch to use: `"lzaCodeRepositoryBranch": "release/v1.12.6"`
96-
4. Follow the remaining steps of the upgrade. This configuration will be used when you install LZA using the `yarn run lza-prep` command in the [Upgrade phase](./upgrade/install-lza.md)
95+
3. Add the following property to the file to specify which branch to use: `"lzaCodeRepositoryBranch": "release/<version>"`
96+
4. Add the following property to specify the path of the CloudFormation installer template from the solution reference bucket `"lzaInstallerTemplateKey": "landing-zone-accelerator-on-aws/<version>/AWSAccelerator-InstallerStack.template"`
97+
5. Follow the remaining steps of the upgrade. This configuration will be used when you install LZA using the `yarn run lza-prep` command in the [Upgrade phase](./upgrade/install-lza.md)
9798

98-
**Note:** If you are upgrading Non-Production and Production environments we recommend that you use the same version for both environments to replicate the same results. You can update to the latest LZA version once you upgraded from ASEA to LZA.
99+
!!! info
100+
The `lzaCodeRepositoryBranch` and `lzaInstallerTemplateKey` should match the same LZA version. For example, to install version `v1.12.6` you should have the following properties in your `input-config.json` file.
101+
102+
```json
103+
"lzaCodeRepositoryBranch": "release/v1.12.6",
104+
"lzaInstallerTemplateKey": "landing-zone-accelerator-on-aws/v1.12.6/AWSAccelerator-InstallerStack.template"
105+
```
106+
107+
The latest CloudFormation installer template is available from the [LZA Implementation Guide](https://docs.aws.amazon.com/solutions/latest/landing-zone-accelerator-on-aws/aws-cloudformation-template.html). Previous versions are accessible by changing the version number in the Url.
108+
109+
110+
!!! tip "When to use a specific version"
111+
If you are upgrading Non-Production and Production environments we recommend that you use the same version for both environments to replicate the same results. You can update to the latest LZA version once you upgraded from ASEA to LZA.

0 commit comments

Comments
 (0)