> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-ecs-services/step-5-test-application.md).
# Step 6: Test the Application
You can test your application using the **DNS Name** from the **Services** page.
*Estimated time to complete Step 6 and finish tutorial: 5 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](/docs/automation-platform/overview/quick-start/step-1-infrastructure.md) exist, both with the name **NONPROD**.
* The **NONPROD** infrastructure has [ECS **Enabled**](/docs/automation-platform/overview/quick-start/step-1-infrastructure.md#check-your-work).
* A Tenant named [**dev01** has been created](/docs/automation-platform/overview/quick-start/step-2-tenant.md).
* A [Task Definition](/docs/automation-platform/overview/quick-start/quick-start-ecs-services/step-4-create-app-via-ecs.md) named **sample-task-def** has been created.
* The [ECS Service (](/docs/automation-platform/overview/quick-start/quick-start-ecs-services/step-5-create-the-ecs-service-and-load-balancer.md)**sample-httpd-app**) and Load Balancer have been created.
## Testing the Application
1. In the **Tenant** list box, select the **dev01** Tenant that you created.
2. Navigate to **Cloud Services** -> **ECS**.
3. Click the **Service Details** tab.
4. In the **DNS Name** card, click the Copy Icon ( ) to copy the DNS address to your clipboard.
Service Details tab with DNS Name card highlighted
4. Open a browser and paste the DNS address in the URL field of your browser.
5. Press **ENTER**. A web page with the text **It works!** displays, from the JavaScript program residing in your Docker Container that is running in **sample-httpd-app**, which is exposed to the web by your Application Load Balancer.
Web page with Hello World! displayed
{% hint style="info" %}
It can take from five to fifteen (5-15) minutes for the Domain 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](/docs/automation-platform/overview/quick-start/step-1-infrastructure.md) named **NONPROD**, a Virtual Private Cloud instance, backed by an ECS-enabled Kubernetes cluster.
* [Created a Tenant](/docs/automation-platform/overview/quick-start/step-2-tenant.md) named **dev01** in Infrastructure **NONPROD**. While generating the Infrastructure, DuploCloud created a set of templates ([Plan](/docs/automation-platform/overview/quick-start/step-1-infrastructure.md)) to configure multiple AWS and Kubernetes components needed for your environment.
* [Created a Task Definition](/docs/automation-platform/overview/quick-start/quick-start-ecs-services/step-4-create-app-via-ecs.md) named **sample-task-def**, used to create a service to run your application.
* [Created a Service](/docs/automation-platform/overview/quick-start/quick-start-eks-services/step-5-create-app-via-k8s.md) named **sample-httpd-app** to connect the Docker containers and associated images, in which your application code resides, to the DuploCloud Tenant environment. In the same step, you c[reated an ALB Load Balancer Listener](/docs/automation-platform/overview/quick-start/quick-start-ecs-services/step-5-create-the-ecs-service-and-load-balancer.md) 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. When you are ready, 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](broken://pages/5Hv1kjjuWKLmR6VU2dKG), and then return to this page. As you learned, the Tenant segregates all work in one isolated environment, so deleting the Tenant 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](/docs/automation-platform/overview/use-cases.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-ecs-services/step-5-test-application.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.