> 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-1/quick-start/create-a-service-with-gke-autopilot.md).

# Create a Service with GKE Autopilot

Finish the Quick Start Tutorial by creating a Service using GKE Autopilot

In this tutorial for DuploCloud AWS, you have so far created a VPC network with configuration templates ([Infrastructure and Plan](/docs/automation-platform/overview-1/quick-start/step-1-infrastructure.md)) and an isolated workspace ([Tenant](/docs/automation-platform/overview-1/quick-start/step-2-tenant.md)).

Now you need to create a DuploCloud Service on top of your Infrastructure and configure the Service to run and deploy your application. In this tutorial path, we'll deploy using Docker containers, leveraging Google Cloud Platform's (GCE) Google Kubernetes Engine (GKE) Autopilot.

Alternatively, you can finish this tutorial by:

* [Creating a DuploCloud Service using GCE's GKE S](broken://pages/30DoAjkzaRTATeeq673S)[tandard.](broken://pages/30DoAjkzaRTATeeq673S)

For a comparison of the benefits of GKE Autopilot vs. GKE Standard, consult this [Google Cloud article](https://cloud.google.com/kubernetes-engine/docs/resources/autopilot-standard-feature-comparison).

*Estimated time to complete remaining tutorial steps: 15-20 minutes*

## Deploying a GKE Standard Service in DuploCloud

For the remaining steps in this tutorial, you will:

1. Create a Service and applications (**webapp)** using the premade Docker image `nginx:latest.`
2. Expose the Service by creating and sharing a load balancer and DNS name.
3. Test the application.


---

# 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-1/quick-start/create-a-service-with-gke-autopilot.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.