> 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.md).

# Creating an ECS Service

Finish the Quick Start Tutorial by creating an ECS Service

This section of the tutorial shows you how to deploy a web application with [AWS Elastic Container Service (ECS)](https://aws.amazon.com/ecs/).

For a full discussion of the benefits of using EKS vs. ECS, consult[ this AWS blog](https://aws.amazon.com/blogs/containers/amazon-ecs-vs-amazon-eks-making-sense-of-aws-container-services/).

{% hint style="info" %}
Instead of creating a DuploCloud Service with AWS ECS, you can alternatively finish the tutorial by:

* [Creating an AWS EKS Service in DuploCloud](/docs/automation-platform/overview/quick-start/quick-start-eks-services.md) running Docker containers or
* [Creating a DuploCloud native Docker Service](/docs/automation-platform/overview/quick-start/quick-start-duplocloud-docker-services.md).
  {% endhint %}

## Deploying an AWS ECS Service in DuploCloud

Unlike AWS EKS, creating and deploying services and apps with ECS requires creating a [Task Definition](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html), a blueprint for your application. Once you create a Task Definition, you can run it as a Task or as a Service. In this tutorial, we run the Task Definition as a Service.

To deploy your app with AWS ECS in this ECS tutorial, you:

1. Create a **Task Definition** using ECS.
2. Create a DuploCloud Service named **webapp**, backed by a Docker image.
3. Expose the app to the web with a **Load Balancer**.
4. Complete the tutorial by testing your application.

*Estimated time to complete remaining tutorial steps: 30-40 minutes*

## Network Architecture and Configurations

Behind the scenes, the topology that DuploCloud creates resembles this low-level configuration in AWS.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2F6s2y2cljNGtVboGRjOx1%2Fimage.png?alt=media&amp;token=12afc74b-c755-4f4a-a846-7cae5888bdb9" alt=""><figcaption><p>AWS ECS Deployment</p></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/automation-platform/overview/quick-start/quick-start-ecs-services.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
