--- title: "Setting Up an AWS Application Load Balancer (ALB)" slug: "understanding-aws-application-load-balancer-alb" tags: ["AWS", "Configuration", "Firewall", "Nasuni Edge Appliance", "Web Access"] updated: 2025-12-12T16:02:58Z published: 2025-12-12T16:02:58Z canonical: "docs.nasuni.com/understanding-aws-application-load-balancer-alb" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.nasuni.com/llms.txt > Use this file to discover all available pages before exploring further. # Setting Up an AWS Application Load Balancer (ALB) ## How to Set Up an AWS Application Load Balancer Setting up an Application Load Balancer (ALB) in AWS requires certain prerequisites and a series of steps to ensure proper configuration. Follow this guide to set up your ALB efficiently. ### Prerequisites - NEA should already be deployed in AWS EC2. - NEA should join NMC. - A certificate should already be created. - Access to DNS to set up the FQDN. - Full access to Amazon EC2. ### Configuring the Load Balancer To set up the load balancer, follow these steps: 1. Log in to the [AWS Console](https://console.aws.amazon.com/). 2. Navigate to the **EC2** section. 3. From the left-side menu, navigate to **Load Balancing** and click **Target Groups**. 4. Click **Create target group**. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-NS7UN79Y.png?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D) 5. Under **Create target group**, click the **Instances** radio button. ![Screenshot showing the creation of a target group](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/AWSALB_004_20251022_213443.jpg?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D) 6. Enter a **Target group name**. 7. Click the **Protocol** drop-down and select **HTTPS.** 8. In the **Port** field, enter “443“. 9. Under **IP address type**, click the **IPv4** radio button. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-HT1TRNGQ.png?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D) 10. Click the **VPC** drop-down and choose the VPC that the instance is currently running in. 11. Under **Protocol version**, click the **HTTP1** radio button. 12. Under **Health check protocol**, select **HTTPS**. 13. In the **Health check path**, enter “/fs/auth/login“. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-74BSXBBO.png?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D) 14. Click **Next**. 15. On the **Register Targets** page, select the Nasuni Edge Appliance that is running Web Access. 16. Click **Include as pending below**. 17. Scroll to the bottom of the page and click **Create target group**. 18. From the left-side menu, navigate to **Load Balancing** and click **Load Balancers**. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-HOD08V0G.png?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D) 19. Under **Application Load Balancer,** click Create.![Screenshot showing the creation of an Application Load Balancer](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/AWSALB_012_20251022_213443.jpg?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D) 20. Enter a **Load balancer name**. 21. Under **Scheme**, choose **Internet-facing**. 22. Under **Load balancer IP address type**, click **IPv4.** 23. Click the **VPC** drop-down and select the VPC with internal access. 24. Under **Availability zones and subnets**, choose at least two subnets. 25. Using the **Security groups** drop-down, choose a security group that has access to HTTP and HTTPS. 26. Under **Listeners and routing**, navigate to the **Protocol** field and select **HTTPS** from the drop-down. 27. In the **Port** field, enter “443“. 28. Under **Routing action,** choose the **Forward to target groups** option. 29. Use the **Target group** drop-down to select the previously created Web Access target group. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-MDND5KHY.png?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D) 30. Scroll down to **Secure listener settings**, click the **Policy name** drop-down, and select the latest TLS policy. 31. Under **Default SSL/TLS server certificate**, choose to have AWS create a certificate or import a certificate. 1. If importing a certificate, enter the **Certificate private key, Certificate body,** and **Certificate chain**. > ***Note****: Do not check the Mutual authentication (mTLS) checkbox.* 32. Click **Create load balancer**. 33. (Optional) To automatically redirect HTTP traffic to HTTPS, follow these steps: 1. Click **Add listener**. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-X54F103R.png?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D) 2. From the **Protocol** drop-down, select **HTTP**. 3. From the **Port** drop-down, select **80**. 4. Under the **Routing action**, click the **Redirect to URL** option. 5. Under **Redirect to URL**, click **Full URL**. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-DQDDDGY1.png?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D) 6. Click **Add listener**. 7. From the left-side menu, under **Load Balancing**, click **Target Groups**. 8. Select **WebAccess**. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-0YZRMNJS.png?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D) 9. Confirm that the target group's **Health status** displays “**Healthy**”. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-VO5ZOEE0.png?sv=2026-02-06&spr=https&st=2026-10-15T02%3A24%3A09Z&se=2026-10-15T03%3A24%3A09Z&sr=c&sp=r&sig=AAcZFewvG88b3xQ%2BVziPN9%2BRUIp%2Fwv5aNjdocnQxI%2Bw%3D)