> For the complete documentation index, see [llms.txt](https://waap.docs.link11.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waap.docs.link11.com/v2.20.2/marketplace-onboarding/aws/aws-version-upgrade.md).

# AWS Version Upgrade

How to upgrade Reblaze BYOL

#### Procedure Overview

<table data-header-hidden><thead><tr><th width="86"></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>#</strong></td><td><strong>Step</strong></td><td><strong>Executed by</strong></td><td><strong>Comments</strong></td><td><strong>Estimated duration</strong></td></tr><tr><td>1.</td><td>Console creation</td><td>Reblaze</td><td>Configuration migration</td><td>1 day</td></tr><tr><td>2.</td><td>Create new deployment</td><td>Customer</td><td>Creating a new instance group</td><td>30 minutes</td></tr><tr><td>3.</td><td>Setup canary instance</td><td>Reblaze<br>&#x26; Customer</td><td>Adding a new template</td><td>15 minutes</td></tr><tr><td>4.</td><td>Verify traffic monitoring</td><td>Reblaze<br>&#x26; Customer</td><td>Verifying there are no issues with site performance, and making changes to security profiles, if necessary.</td><td>1 hour</td></tr><tr><td>5.</td><td>Rеmove old template</td><td>Customer</td><td>Replace all instances</td><td>15 minutes</td></tr></tbody></table>

### Procedure Details

#### Step 1: Console Creation by Reblaze

The Reblaze team will set up a new 2.x console for you. Once this is done, proceed to Step 2.

Redis settings: If you already have a Redis server installed (which is usually true for Reblaze installations of v2.14 and later), you do not need to create a new one. If you do not have a Redis server setup, you will need to create one.

**Step 2: Create New Deployment**

Go to EC2 > Auto Scaling groups, see **Launch template configuration** ( zone , capacity, type, etc.)

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FA999OtruT7wZAQqrNLoQ%2Fimage.png?alt=media\&token=dbfc984d-e666-4145-9915-ccb336e9886f)

Now go to EC2 > Launch Template Select your template. To create a new launch template version with a new image, click **Actions > Modify template**

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FGidxGwwG4VhUWEdSrQSj%2Fimage.png?alt=media\&token=33b44768-ab0a-404b-af0d-5ce7d2babd6b)

On the screen that appears (below), provide a description of the image (version 2.18.0 was used as an example below):

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FZfSgNCNs6EkyHwFvdYu1%2Fimage.png?alt=media\&token=45fc95bf-a0eb-41bd-ab92-d869e43157b5)

Scroll further down the page and see the AMI details listed in the **AMI from catalog** tab:

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2Fd3dbRFYYHqsYfKQ7SyMA%2Fimage.png?alt=media\&token=f869c3dd-29ce-47d4-b437-aaaa05da11dc)

Next, Reblaze deployment in the AWS marketplace must be set up.

Search for Reblaze and click on the first option.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FovW2gWfpoz5oAl3LURwb%2Fimage.png?alt=media\&token=446dc32f-dd0a-4996-ace3-e3a2b06a7dd8)

Scroll down the page and click **View CloudFormation Template.**

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FluzNeB5H9sQqhXc6i6Wb%2Fimage.png?alt=media\&token=1fddfb9a-740a-4894-aea0-21cb824485aa)

Now click **View Template in CloudFormation Designer**.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FL9nAc98lrxADPTH6E7br%2Fimage.png?alt=media\&token=0e45b600-260f-4cec-81b9-621a193676f3)

In this template (below) you can see each region and its AMI.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FtdO1AnA5HNu1OXfnNRtB%2Fimage.png?alt=media\&token=c30b8356-4278-4f7b-9866-f75b41dd3aa9)

Copy the AMI compatible with your region. (In our example we used the “us-east-1” AMI.)

Now, return  to the Modify template window. Under AMI from catalog, select Browse more AMI&#x73;**.**

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FC5ogR8GDYM5RM33wcenB%2Fimage.png?alt=media\&token=938ca941-d4ad-40d9-bd63-a4dc4cfd8637)

Paste the AMI in the search box. Choose the Reblaze image from among the search results.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FEPht4ou5WmGVeOqoZpyP%2Fimage.png?alt=media\&token=f5bba824-01ac-45c8-bca9-daf625055d4b)

Find and select the Reblaze image.\
Click **Select.**

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2Fzy3uBMIaLdm8oX8rKCN1%2Fimage.png?alt=media\&token=4b18c3a7-ca0e-4685-b448-84d36310bdfe)

In the Modify template window, add the new version to your catalog.&#x20;

Click Create template version on the bottom right of the screen.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FP7a349rWAldDbcuk6FFN%2Fimage.png?alt=media\&token=3b54c2f3-0164-4610-b5f9-1c8a6bae364d)

Your new version now appears under **Launch template details.**

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FoxFQJ2zlX2cAfK2tlJ98%2Fimage.png?alt=media\&token=494cb03a-952a-470d-888d-da5c06f8335d)

#### **Step 3: Set Up Canary Instance**

Go to EC2 > Launch template and change the Default to the new version (2) Click Update.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FuOLNs4C1d5v3cdhB1v1K%2Fimage.png?alt=media\&token=d7bd2281-5af4-4867-a549-494a26aa37e6)

Go to your AutoScaling group. In the **Details** tab, find Group details and click **Edit.**

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FyWhfOKb5IdCxWZFwVTiJ%2Fimage.png?alt=media\&token=4dcf387c-57b4-44aa-978a-d4c86efbafbc)

**Desired capacity** must be increased by 100% . For example, if you have 2 servers, Desired capacity must be set to 4. Ensure that this amount does not exceed the Maximum capacity or it too will need to be increased.

Click **Update** (below).

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2Fe8MYy9hyS4J417H3Oid9%2Fimage.png?alt=media\&token=827ebdfa-dd80-4329-9820-3cd4e5466bda)

#### **Step 4: Verify Traffic Monitoring**

On the EC2 > Auto Scaling groups screen, check the **Instance management** tab for the number of servers. Alternatively, you can check the number of servers on your console.&#x20;

You should be able to see new servers being added with the new version.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2Fhm7kkrbl0n9d1CxaPEeZ%2Fimage.png?alt=media\&token=8930ac14-3aaa-4c96-8c58-c18b6e7e593b)

Go to your Reblaze dashboard and confirm that you see the new instances and that traffic is routing through them and your sites are working as expected.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FVM0DXAhGimgU1IjN1UTu%2Fimage.png?alt=media\&token=20389ed6-c420-4190-b545-4e6b07efb960)

#### **Step 5: Remove Old Servers**

Once we verify the new servers are receiving traffic, the old version and its servers must be terminated.

Under the Auto Scaling group, **Details** tab, there is an Advanced configurations window.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FkFkQPrfcdwfKIR42hDgC%2Fimage.png?alt=media\&token=bf8ee204-e3e6-4ede-89a0-6ce8044d612f)

Make sure Termination policies is set to Oldest Launch Template; if not, click Edit and             change the policy.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FL1pOPTUqyXw3BUQeE9Uq%2Fimage.png?alt=media\&token=522ab1d8-5fa1-4f68-9fca-4928bd967936)

Under the Details tab on the EC2 > Auto Scaling groups screen, locate the **Group size** options.  Reduce the number of desired servers in group to the original amount.

![](https://865091150-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0roddwHI2wUZTmqjZrkz%2Fuploads%2FCuCTjwLQL99cH8xkQpwp%2Fimage.png?alt=media\&token=b53a5a50-0a29-431a-8578-305f28c93e7d)

Click **Update**. The servers attached to the older version will terminate.