You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/nginx/deployment-guides/amazon-web-services/ingress-controller-elastic-kubernetes-services.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ The `PREFIX` argument specifies the repo name in your private container registry
33
33
34
34
35
35
<spanid="amazon-eks"></span>
36
-
## Creating an Amazon EKS Cluster
36
+
## Create an Amazon EKS Cluster
37
37
You can create an Amazon EKS cluster with:
38
38
- the AWS Management Console
39
39
- the AWS CLI
@@ -46,7 +46,7 @@ This guide covers the `eksctl` command as it is the simplest option.
46
46
2. Create an Amazon EKS cluster by following the instructions in the [AWS documentation](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html). Select the <spanstyle="white-space: nowrap; font-weight:bold;">Managed nodes – Linux</span> option for each step. Note that the <spanstyle="white-space: nowrap;">`eksctl create cluster`</span> command in the first step can take ten minutes or more.
47
47
48
48
<spanid="amazon-ecr"></span>
49
-
## Pushing the NGINX Plus Ingress Controller Image to AWS ECR
49
+
## Push the NGINX Plus Ingress Controller Image to AWS ECR
50
50
51
51
This step is only required if you do not plan to use the prebuilt NGINX Open Source image.
52
52
@@ -81,7 +81,7 @@ This step is only required if you do not plan to use the prebuilt NGINX Open Sou
81
81
```
82
82
83
83
<spanid="ingress-controller"></span>
84
-
## Installing the NGINX Plus Ingress Controller
84
+
## Install the NGINX Plus Ingress Controller
85
85
86
86
Use [our documentation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) to install the NGINX Plus Ingress Controller in your Amazon EKS cluster.
87
87
@@ -97,15 +97,15 @@ You need a Kubernetes `LoadBalancer` service to route traffic to the NGINX Ingre
97
97
98
98
We also recommend enabling the PROXY Protocol for both the NGINX Plus Ingress Controller and your NLB target groups. This is used to forward client connection information. If you choose not to enable the PROXY protocol, see the [Appendix](#appendix).
99
99
100
-
### Configuring a `LoadBalancer` Service to Use NLB
100
+
### Configure a `LoadBalancer` Service to Use NLB
101
101
102
102
Apply the manifest `deployments/service/loadbalancer-aws-elb.yaml` to create a `LoadBalancer` of type NLB:
0 commit comments