> 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

#### 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="/files/lX4zqnEUu3Ne4Jq2cGUa" 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**

![](/files/orq65DKgvZgrpa8e4jtQ)

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

![](/files/jpJcCs0tMwjuBLBELEo9)

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

![](/files/VHS9jRfwmmfD2R1eAfAS)

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

Search for Reblaze and click on the first option.

![](/files/8xhMvhP0o1lA3c4I42Gv)

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

![](/files/iKBxmo697AISRWTgzJU8)

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

![](/files/z1mVfp2Bn0Kn2PxkUca2)

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

![](/files/yiZfbzZcwfMLboyLAd4I)

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;**.**

![](/files/bD7tecIzUOmBG9QUo58a)

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

![](/files/9DK4UnxIZ5ZFL0NLH4So)

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

![](/files/dlKoWcbB78jAPrIaaYpn)

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

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

![](/files/AMvtVsMgETC47DSZNZo6)

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

![](/files/Tb4ceNCvmSIKvDUuHDkK)

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

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

![](/files/a8rRiNWUeUYasio0oSdo)

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

![](/files/D4Fup1hAu6MpsV5jMhXt)

**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).

![](/files/9vGQHKpd1wdLUSd8Tea3)

#### **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.

![](/files/EBTDicqsa94xBubJpdNe)

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.

![](/files/HjPVf3juoHZ4dixyqeqi)

#### **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.

![](/files/Shsr8hGHFrt9aiQcwKdy)

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

![](/files/Vtl9gR107CgGgQVxwK8U)

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.

![](/files/f34rYk8OmpuJXwLZbCQK)

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