On the Containers tab, verify that the current status is Running.

• An Infrastructure and Plan exist, both named NONPROD.

• The NONPROD infrastructure has EKS Enabled.

• A Tenant named dev01 has been created.

• A Host named .

• A Service named .

• An has been created.

Testing the Application

1. In the Tenant list box, select the dev01 Tenant.

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

3. From the Name column, select demo-service.

4. Click the Load Balancers tab.

5. In the DNS status card, click the Copy Icon ( ) to copy the DNS address displayed to your clipboard.
6. Open a browser instance and Paste the DNS in the URL field of your browser.

7. Press ENTER. A web page with the text Hello World! is displayed, from the JavaScript program residing in your Docker Container running in demo-service, which is exposed to the web by your Load Balancer.

Congratulations! You have just launched your first web service on DuploCloud!

Reviewing What You Learned

In this tutorial, your objective was to create a cloud environment to deploy an application for testing purposes, and to understand how the various components of DuploCloud work together.

The application rendered a simple web page with text, coded in JavaScript, from software application code residing in a Docker container. You can use this same procedure to deploy much more complex cloud applications.

In the previous steps, you:

• Created a DuploCloud Infrastructure named NONPROD: a Virtual Private Cloud instance backed by an EKS-enabled Kubernetes cluster.

• Created a Tenant named dev01 in Infrastructure NONPROD. While generating the Infrastructure, DuploCloud created a set of templates (Plan) to configure multiple AWS and Kubernetes components needed for your environment.

• named host01, providing the application with storage resources.

• named demo-service to connect the Docker containers and associated images housing your application code to the DuploCloud Tenant environment.

• to expose your application via ports and backend network configurations.

• as expected by testing the DNS Name exposed by the Load Balancer Listener.

Cleaning Up Your Tutorial Environment

In this tutorial, you created many artifacts for testing purposes. Now that you are finished, clean them up so others can run this tutorial using the same names for Infrastructure and Tenant.

1. To delete the dev01 tenant follow these instructions, then return to this page. As you learned, the Tenant segregates all work in one isolated environment, so deleting the Tenant you created cleans up most of your artifacts.

2. Finish by deleting the NONPROD Infrastructure. In the DuploCloud Portal, navigate to Administrator -> Infrastructure. Click the Action menu icon () for the NONPROD row and select Delete.

The NONPROD Infrastructure is deleted and you have completed the clean-up of your test environment.

Thanks for completing this tutorial and proceed to the next section to learn more about using DuploCloud with AWS.

Estimated time to complete Step 8: 5 minutes.

Prerequisites

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

• An Infrastructure and Plan exist, both named NONPROD.

• The NONPROD infrastructure has EKS Enabled.

• A Tenant named dev01 has been created.

• A Host named .

• A Service named .

• An has been created.

Creating a Custom DNS Name

1. In the Tenant list box, select the dev01 Tenant.

2. Navigate to Kubernetes -> Services. The Services page displays.

3. From the Name column, select demo-service.

4. Click the Load Balancers tab. The ALB Load Balancer configuration is displayed.

5. In the DNS Name card, click Edit. The prefix in the DNS Name is editable.

6. Edit the DNS Name and select a meaningful DNS Name prefix.

7. Click Save. A success message briefly displays at the top center of the DuploCloud Portal.

An entry for your new DNS name is now registered with demo-service.

Checking Your Work

1. Navigate to Kubernetes -> Services.

2. From the Name column, select demo-service.

3. Select the Load Balancers tab and verify that the DNS Name card displays your modified DNS Name.

• Enable access logging to monitor HTTP message details and record incoming traffic data. Access logs are crucial for analyzing traffic patterns and identifying potential threats, but they are not enabled by default. You must manually activate them in the Load Balancer settings.

• Protect against requests that contain invalid headers.

Estimated time to complete Step 7: 5 minutes.

Prerequisites

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

• An Infrastructure and Plan exist, both named NONPROD.

• The NONPROD infrastructure has EKS Enabled.

• A Tenant named dev01 has been created.

• A Host named .

• A Service named .

• An has been created.

Securing the Load Balancer

1. In the Tenant list box, select the dev01 Tenant.

2. In the DuploCloud Portal, navigate to Kubernetes -> Services.

3. From the NAME column, select the Service (demo-service).

4. Select the Load Balancers tab.

5. In the Other Settings card, click Edit. The Other Load Balancer Settings pane displays.
6. Select the Enable Access Logs and Drop Invalid Headers options.
7. Accept the remaining default settings and click Save. The settings are updated.

Checking Your Work

1. In the Tenant list box, select the dev01 Tenant.

2. In the DuploCloud Portal, navigate to Kubernetes -> Services.

3. From the NAME column, select the Service (demo-service).

4. Select the Load Balancers tab.

5. 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

Enabling access logs enhances the security and monitoring capabilities of your Load Balancer and provides insights into the traffic accessing your application, for a more robust security posture.