|
9 | 9 | - how-to |
10 | 10 | --- |
11 | 11 |
|
12 | | -This guide explains how to create a highly available (HA) active‑passive deployment of F5 NGINX Plus in the [Amazon Web Services](https://aws.amazon.com/) (AWS) cloud. It combines the `keepalived`‑based solution for high availability (provided by NGINX for on‑premises HA deployments) with the AWS Elastic IP address feature. |
13 | | - |
| 12 | +This guide explains how to create a high availability (HA) active‑passive deployment of F5 NGINX Plus in the [Amazon Web Services](https://aws.amazon.com/) (AWS) cloud. It combines the `keepalived`‑based solution for high availability (provided by NGINX for on‑premises HA deployments) with the AWS Elastic IP address feature. |
14 | 13 | NGINX also provides a [solution for active‑active HA of NGINX Plus in AWS]({{< ref "high-availability-network-load-balancer.md" >}}), using AWS Network Load Balancer. |
15 | 14 |
|
16 | 15 | <span id="ha-aws_overview"></span> |
17 | 16 | ## Overview |
18 | 17 |
|
19 | 18 | The [supported solution for HA deployment]({{< ref "nginx/admin-guide/high-availability/ha-keepalived.md" >}}) of NGINX Plus that uses `keepalived` is designed for on‑premises deployments. It is typically not viable in cloud environments, such as AWS, because of the networking restrictions they impose. |
20 | 19 |
|
21 | | -One method for deploying NGINX Plus in a highly available manner on AWS is to use ELB in front of NGINX Plus instances. However, the method has several disadvantages: |
| 20 | +One method for deploying NGINX Plus in a highly available manner on AWS is to use ELB in front of NGINX Plus instances. But, the method has several disadvantages: |
22 | 21 |
|
23 | 22 | - It increases the cost of your deployment. |
24 | 23 | - It limits the number of protocols NGINX Plus and your applications can support. In particular, ELB does not support UDP load balancing. |
@@ -69,14 +68,14 @@ The scripts in the HA solution use the AWS API to associate an Elastic IP addre |
69 | 68 | 3. Attach this IAM role to the instance. |
70 | 69 |
|
71 | 70 | <span id="ha-aws_eip"></span> |
72 | | -## Step 2 – Allocate an Elastic IP Address |
| 71 | +## Step 2 – Allocate an Elastic IP address |
73 | 72 |
|
74 | 73 | Allocate an Elastic IP address and remember its ID. For detailed instructions, see the [AWS documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating). |
75 | 74 |
|
76 | 75 | <span id="ha-aws_keepalived-install"></span><span id="ha-aws_step3"></span> |
77 | 76 | ## Step 3 – Install `keepalived`, `wget`, and the AWS CLI |
78 | 77 |
|
79 | | -1. Install two packages from your OS vendor’s repository: the **keepalived** package and **wget**, which is used by the HA scripts. |
| 78 | +1. Install two packages from your OS vendor’s repository: **keepalived** and **wget**, which is used by the HA scripts. |
80 | 79 |
|
81 | 80 | - On Ubuntu systems: |
82 | 81 |
|
@@ -155,7 +154,7 @@ vrrp_instance VI_1 { |
155 | 154 | } |
156 | 155 | ``` |
157 | 156 |
|
158 | | -You must change values for the following configuration keywords (as you do so, also remove the angle brackets enclosing the placeholder value): |
| 157 | +You must change values for the following configuration keywords. As you do so, also remove the angle brackets enclosing the placeholder value: |
159 | 158 |
|
160 | 159 | - `script` in the `chk_nginx_service` block – The script that sends health checks to NGINX Plus. |
161 | 160 |
|
|
0 commit comments