Step 4: Create and start the failover load balancer

a) Update the existing load balancer (ALB)

1. Navigate to the Load Balancing service and click Edit on the first load balancer.

1. Update the Hostname to the one you used as DNS alias in step 3 and click Save Load Balancer

1. Deselect the second application (hosted on the APP2 server) from Application Endpoints

We're associating ALB with APP1 and Failover ALB with APP2 for demo purposes only. This will allow you to see which of the load balancers is serving the request. In a typical scenario you may want to associate all load balancers with all applications to maximize resilience.

1. Click Save Load Balancer

b) Create the new load balancer (Failover ALB)

1. Click Add new Application Load Balancer

2. Set the Host server as Failover ALB (this is a name of the server we onboarded in step 1)

1. Update the Hostname to the one you used as DNS alias in step 3

1. Deselect the first application (hosted on the APP1 server) from Application Endpoints

We're associating ALB with APP1 and Failover ALB with APP2 for demo purposes only. This will allow you to see which of the load balancers is serving the request. In a typical scenario you may want to associate all load balancers with all applications to maximize resilience.

1. Click Save Load Balancer

c) Apply changes to both load balancers (ALB and Failover ALB)

1. For each of load balancers: Click Restart Load Balancer, then provide Root password and click OK

1. Verify that both of the load balancers are active and have the new URL "in config" after restart.

1. (Optional) If you configured Gateway Security or Endpoints Security for the first load balancer, configure it for the second one too. Otherwise you can skip this step.

3️⃣Secure the data in-transit with SSL