> 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/prerequisites/initial-infrastructure-setup.md).
# Initial Infrastructure Setup
Set up the initial DuploCloud Infrastructure
Once your GCP project has been added to the DuploCloud Portal, the next step is to set up the first Infrastructure.
## Creating an Initial Infrastructure
1. From the DuploCloud Portal, navigate to **Administrator** -> **Infrastructure**, and click **Add**.
2. Give the Infrastructure a **Name**, e.g., nonprod.
3. Select the appropriate **Account**.
4. Enter the **VPC CIDR**, e.g., 10.30.0.0/16 (Note: A /16 CIDR block is recommended for Kubernetes to accommodate its IP address requirements).
5. From the **Cluster Mode** list box, select **GKE Standard**.
6. From the **GKE Endpoint Visibility** list box, select **Public** (for production Infrastructures, set visibility to **Private**).
7. For the remaining fields, keep the default values.
The Add Infrastructure page in the DuploCloud Portal
The Infrastructure page in the DuploCloud Portal
8. Click **Create**. It will take approximately 15 to 20 minutes for the setup to complete. Monitor faults to see if any issues arise (NTP clock sync faults can be ignored).
{% hint style="info" %}
When the Infrastructure setup is complete, a Plan with the same name as the infrastructure displays on the Plans page (**Administrators** -> **Plans**).
{% endhint %}
---
# 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/prerequisites/initial-infrastructure-setup.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.
