diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-05 03:07:52 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-05 03:07:52 +0000 |
commit | a0c1ba61c8e8c9195e3ad4deefc5c4cb5c6a1501 (patch) | |
tree | 0731210fac047fdfb04a8e907701e0efab8c897e /doc/install/aws | |
parent | 77237c5a6b9044f58beabc54d3589e5fa09cbfba (diff) | |
download | gitlab-ce-a0c1ba61c8e8c9195e3ad4deefc5c4cb5c6a1501.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/install/aws')
-rw-r--r-- | doc/install/aws/index.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/install/aws/index.md b/doc/install/aws/index.md index 23c609b29a9..b5e2db40dd7 100644 --- a/doc/install/aws/index.md +++ b/doc/install/aws/index.md @@ -293,11 +293,11 @@ On the EC2 dashboard, look for Load Balancer in the left navigation bar: 1. Click the **Create Load Balancer** button. 1. Choose the **Classic Load Balancer**. - 1. Give it a name (`gitlab-loadbalancer`) and for the **Create LB Inside** option, select `gitlab-vpc` from the dropdown menu. + 1. Give it a name (we'll use `gitlab-loadbalancer`) and for the **Create LB Inside** option, select `gitlab-vpc` from the dropdown menu. 1. In the **Listeners** section, set HTTP port 80, HTTPS port 443, and TCP port 22 for both load balancer and instance protocols and ports. 1. In the **Select Subnets** section, select both public subnets from the list. 1. Click **Assign Security Groups** and select **Create a new security group**, give it a name - (`gitlab-loadbalancer-sec-group`) and description, and allow both HTTP and HTTPS traffic + (we'll use `gitlab-loadbalancer-sec-group`) and description, and allow both HTTP and HTTPS traffic from anywhere (`0.0.0.0/0, ::/0`). 1. Click **Configure Security Settings** and select an SSL/TLS certificate from ACM or upload a certificate to IAM. 1. Click **Configure Health Check** and set up a health check for your EC2 instances. |