Step 7: Enable additional options for the Load Balancer (optional)

Adding a security layer and enabling other options for your Load Balancer

This step is optional and not necessary to run the example application in this tutorial.

However, while it's not as important to secure a load balancer for a small web application in a tutorial, your production cloud apps require an elevated level of protection.

To set up a Web Application Firewall (WAF) for a production application, follow the steps in the Web Application Firewall procedure. You won't set up a WAF in this tutorial.

Otherwise, to skip this step, proceed to the next page in this tutorial.

In this tutorial step, for the Application Load Balancer (ALB) you created in Step 6, you will:

Estimated time to complete Step 7: 5 minutes.


Before securing a Load Balancer, verify that you accomplished the tasks in the previous tutorial steps. Using the DuploCloud Portal, confirm that:

Select the Tenant you created

In the Tenant list box, on the upper-left side of the DuploCloud Portal, select the dev01 Tenant that you created.

Securing the Load Balancer

  1. In the DuploCloud Portal, navigate to Kubernetes -> Services. The Services page displays.

  2. From the Name column, select the Service to which your Load Balancer is attached (demo-service).

  3. Click the Load Balancers tab.

  4. In the Other Settings card, click Edit. The Other Load Balancer Settings pane displays.

  1. In the Web ACL list box, select None, because you are not connecting a Web Application Firewall.

  2. For this tutorial, select only the Enable Access Logs and Drop Invalid Headers options.

  3. Accept the Idle Timeout default setting and click Save. The Other Settings card in the Load Balancers tab is updated with your selections.

Checking your work

Verify that the Other Settings card contains the selections you made above for:

  • Web ACL - None

  • HTTP to HTTPS Redirect - False

  • Enable Access Logs - True

  • Drop Invalid Headers - True

Last updated


© DuploCloud, Inc. All rights reserved. DuploCloud trademarks used herein are registered trademarks of DuploCloud and affiliates