# Step 9: Test the Application

You can test your application directly from the **Services** page using the **DNS** status card.

*Estimated time to complete Step 9 and finish tutorial: 10 minutes.*

## Prerequisites

Before testing your application, verify that you accomplished the tasks in the previous tutorial steps. Using the DuploCloud Portal, confirm that:

* An [Infrastructure and Plan](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/step-1-infrastructure) exist, both named **NONPROD**.
* The **NONPROD** infrastructure has EKS[ **Enabled**](https://docs.duplocloud.com/docs/automation-platform/overview/step-1-infrastructure#check-your-work).
* A Tenant named [**dev01** has been created](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/step-2-tenant).
* A Host named [**host01** has been created](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-eks-services/step-3-create-host).
* A Service named [**demo-service** has been created](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-eks-services/step-5-create-app-via-k8s).
* An [HTTPS Application Load Balancer](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-eks-services/step-6-create-a-load-balancer) has been created.

## Testing the Application

{% hint style="info" %}
Note that if you skipped [Step 7](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-eks-services/step-7-secure-the-load-balancer) and/or [Step 8](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-eks-services/step-8-create-dns-name), the configuration in the **Other Settings** and **DNS** cards appears slightly different from the configuration depicted in the screenshot below. These changes do not impact you in testing your application, as these steps are optional. You can proceed to test your app with no visible change in the output of the deployable application.
{% endhint %}

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 ( <img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FWeIdo7gyB77M5reNRKG1%2Fcopy_icon.png?alt=media&#x26;token=903e9bf7-a294-41ae-97e9-dcb22d848041" alt="" data-size="line"> ) to copy the DNS address displayed to your clipboard.<br>

   <figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2F6PIaoJbR8lmwW34GixBu%2Fconfigured%20new.png?alt=media&#x26;token=50ef579f-9baa-4338-8024-851f05cc14b1" alt=""><figcaption></figcaption></figure>
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.

<div align="left"><figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2F0pyk0bM0eAUuSg02i1ax%2FAWS_QS_29.png?alt=media&#x26;token=9d4e93ef-a722-43be-b773-81745eaa88d0" alt=""><figcaption><p>Web page with <strong>Hello World!</strong> displayed</p></figcaption></figure></div>

{% hint style="info" %}
It can take from five to fifteen (5-15) minutes for the DNS Name to become active once you launch your browser instance to test your application.
{% endhint %}

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](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/step-1-infrastructure) named **NONPROD**: a Virtual Private Cloud instance backed by an EKS-enabled Kubernetes cluster.
* [Created a Tenant](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/step-2-tenant) named **dev01** in Infrastructure **NONPROD**. While generating the Infrastructure, DuploCloud created a set of templates ([Plan](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/step-1-infrastructure)) to configure multiple AWS and Kubernetes components needed for your environment.
* [Created an EC2 host](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-eks-services/step-3-create-host) named **host01**, providing the application with storage resources.
* [Created a Service](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-eks-services/step-5-create-app-via-k8s) named **demo-service** to connect the Docker containers and associated images housing your application code to the DuploCloud Tenant environment.
* [Created an ALB Load Balancer Listener](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-eks-services/step-6-create-a-load-balancer) to expose your application via ports and backend network configurations.
* [Verified that your web page rendered](#testing-the-application) 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](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-eks-services/broken-reference), 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 (<img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FaQe5p7flz0LzZESyhTO4%2Fimage.png?alt=media&#x26;token=90762291-a295-4f1c-a32a-e84f2b7687ee" alt="" data-size="line">) 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](https://docs.duplocloud.com/docs/automation-platform/overview/use-cases).