> 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.md).
# GCP User Guide
Using DuploCloud with Google Cloud Platform
The DuploCloud platform installs a Virtual Machine resource within your GCP Project. It can be accessed using a web interface, API, and a Terraform provider. Log in to the DuploCloud portal via SSO through your GSuite or O365 login.
{% hint style="info" %}
Read through the [DuploCloud Platform Overview](/docs/automation-platform/readme-1.md) and are familiar with DuploCloud terms such as [Infrastructure](/docs/automation-platform/application-focused-interface-duplocloud-architecture/infrastructure.md), [Plan](/docs/automation-platform/application-focused-interface-duplocloud-architecture/plan.md), and [Tenant](/docs/automation-platform/application-focused-interface-duplocloud-architecture/tenant.md).
{% endhint %}
## Prerequisites
Before you begin, ensure that:
* DuploCloud Portal has been set up and you have access to it.
* You have access to your individual Slack or Teams channel for 24x7 support from the DuploCloud team.
Behind the scenes, a topology is created similar to the following low-level configuration in GCP.
DuploCloud Sample Architecture for GCP
---
# 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.md?ask=&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.
