> 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/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="101"></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.)

<img src="https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FFnKuqOjps8gNSgXftFKs%2Fimage.png?alt=media&amp;token=7397d621-8ac5-4a84-a19e-6f5dd66037e3" alt="" data-size="original">

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://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FBq6xURTWYZ0EB9zplNMy%2Fimage.png?alt=media\&token=f0ce9842-7729-45ae-9ae7-24903fc7430a)

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2Fol9tTNxHAgLFIxXwU9aX%2Fimage.png?alt=media\&token=9b7d990d-de0c-435c-b3ac-047f41c9aebf)

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FpNaiGfDmWNcvSGEjsEsK%2Fimage.png?alt=media\&token=52ff1a3a-3de1-4f52-887d-2ac963d4a2f6)

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

Search for Reblaze and click on the first option.

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FShDnovQ6T3DdDkvR3G0E%2Fimage.png?alt=media\&token=f3c02028-c7aa-4426-99ec-b4254a622c12)

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2F7ucVZCE0k6is74rgMcph%2Fimage.png?alt=media\&token=dc952651-1dc8-4456-8d49-3aab318ecacf)

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FNzX5SwRdh7NzP1RaDvFY%2Fimage.png?alt=media\&token=eb596af2-f31f-4d2e-9aa2-027e641435eb)

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FRiXlOxRx3jxwQ5mzraZL%2Fimage.png?alt=media\&token=4d9950d7-c2c4-44f3-a3c7-c835b063cff7)

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://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FG48CZyqVB54V4Rt5FtT0%2Fimage.png?alt=media\&token=9eca6957-b6b4-46b0-9be0-a87870576276)

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FDOFaXv9MhiG3tJGLYIkc%2Fimage.png?alt=media\&token=1c196ca9-929f-4724-822d-69a50a35201b)

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FIXqMdE7LP4z1UGxYez3Q%2Fimage.png?alt=media\&token=0564db57-fbea-434d-a3b9-8b86f5c4fa73)

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://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FqiMYNY7MmpQ4du9ZZuMJ%2Fimage.png?alt=media\&token=f122c57e-91ea-4e5a-8733-9d9a14225b99)

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2Fegos4iQLOTCLc7QGwWMM%2Fimage.png?alt=media\&token=18e111d3-9a42-4f35-ae64-5b637e6ea70c)

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

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FS5OWZoezUdPATsyHKe8Y%2Fimage.png?alt=media\&token=e0a33193-6fad-436e-aa52-cc1272978626)

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2F2z5X80blwsbzYbGW1tlM%2Fimage.png?alt=media\&token=e5c9748f-1621-4be7-bb81-c17de12089d3)

**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://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FkNRwfqner4TmhkFIvgu0%2Fimage.png?alt=media\&token=e9be099a-ef3c-423a-a10a-047d6b59f993)

#### **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://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FF39V2OE71JVMvDFlb7G7%2Fimage.png?alt=media\&token=26310ba1-cd5e-491f-ad40-2e6528f32511)

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://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2F1VXcIQraOAYgtCMFyHWs%2Fimage.png?alt=media\&token=77943353-8c42-4adc-a3da-c16355aac416)

#### **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://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FaZfHFIK8wJRBXtPe7dBz%2Fimage.png?alt=media\&token=5c7cba0b-62ad-48af-aa28-e87a00af7a0c)

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

![](https://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FhwA3q5niZoVBGe3F9pEg%2Fimage.png?alt=media\&token=ced4b999-5984-4d6c-a1db-fc4e9608226f)

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://2672114182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIRmpkGX8y0mvi8hAYhjD%2Fuploads%2FlcZOlVNhDyY1TtTvtpri%2Fimage.png?alt=media\&token=ccb1ba92-ce39-4205-a596-434c71641e22)

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