> 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/marketplace-agents/aws-extension/quick-start/provision-new/step-1-network.md).

# Step 1: Create a Network

Create a Network Baseline — a VPC with public and private subnets across multiple availability zones.

A Network Baseline provisions the VPC that all other resources will run inside. This is the first resource you create.

## What gets created

* A VPC with your chosen CIDR block
* Public and private subnets, one pair per availability zone
* An Internet Gateway for public subnet routing
* NAT Gateways for private subnet outbound access (if enabled)
* Route tables for public and private subnets
* RDS and ElastiCache subnet groups pre-configured for databases
* An all-host security group for the network, created with no inbound rules
* A VPC peering connection to the helpdesk VPC, with routes and an inbound HTTPS rule (if **Peer with helpdesk VPC** is enabled)

## Walkthrough

### Step 1 — Navigate to Network

In the left sidebar, open **Infrastructure Agent** and select **Network**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-27847ac232b9802ffc8a8a25aa6147281af9558f%2Fnetwork-step-01.png?alt=media)

### Step 2 — Network List

The **Networks** page lists every network in the workspace, with summary cards for total, ready, in-progress and needs-attention networks. Use the **AWS**, **Azure** and **GCP** filters to narrow the list. Click **Create network** to begin.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-152a26e21f765bebaa2d0f4929be92d20141a3c2%2Fnetwork-step-02.png?alt=media)

### Step 3 — Network Details

The **Create Network Baseline** wizard opens. Fill in the first page:

* **Name** — a unique identifier for the network (e.g. `prod-vpc-us-east-1`). Letters, numbers and hyphens.
* **Cloud** — select **AWS**
* **Description** — optional
* **Account (Scope)** — the cloud account scope to provision into
* **Metadata** — optional key/value pairs to attach to the network

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-86267375aa9bb3e7080e92aea2a96d4813bfb62e%2Fnetwork-step-03.png?alt=media)

### Step 4 — Network Spec

Define the network configuration. Select **Create new** to provision a fresh VPC, or **Import existing** to register an existing one.

* **Region** — the AWS region (e.g. `us-east-1 — N. Virginia`)
* **VPC CIDR** — the IP range for the VPC (e.g. `10.0.0.0/16`). The platform checks for overlap with existing networks.
* **Availability Zones** — number of AZs to span (`2` or `3`)
* **NAT Gateway** — `One per AZ (High Availability)`, `Single NAT Gateway` (the default), or `None`
* **Customize subnet CIDRs** — off by default. Turn it on to enter your own public and private CIDR for each AZ instead of having them computed. Each CIDR must sit inside the VPC CIDR and not overlap the others.
* **Subnet Prefix** — the prefix length of each subnet (e.g. `24`); must be at least the VPC prefix + 3. Hidden when **Customize subnet CIDRs** is on.
* **Peer with helpdesk VPC** — on by default. Peers the new VPC with the DuploCloud helpdesk VPC so that instances and databases in private subnets are reachable from DuploCloud. When enabled, the VPC CIDR must not overlap the helpdesk VPC or any other network already peered with it.

The **Subnets — computed from CIDR** table previews the private and public subnet CIDRs that will be created per AZ before you submit.

Click **Create & Provision**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-546d682a5d68ed607b27ecca713362c675c60912%2Fnetwork-step-04.png?alt=media)

### Step 5 — Network Detail Page

DuploCloud creates the network and opens its detail page. The header shows the account, region and cloud, and the **Provisioning** panel on the right tracks the network's status. Provisioning runs as an agent ticket: click **Track Status** (or **Ask the Agent** in the header) to open it.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-2575b8fc7e599d33f372bfba8df38840856d29bf%2Fnetwork-step-05.png?alt=media)

### Step 6 — Agent Ticket Opens

The agent uses the `duplo-aws-infra` skill and begins by reading the `aws-network-baseline.md` skill file to load its instructions.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-f450ac20241e505930afd5721a5ad01f7cec49d7%2Fnetwork-step-06.png?alt=media)

### Step 7 — Parameters Parsed

The agent sets up AWS credentials, then parses the network spec into structured parameters:

* `NETWORK_NAME`, `REGION`, `VPC_CIDR`, `azs`, `subnet_mask`
* `NAT_MODE` (e.g. `SingleAz`), `ENABLE_DNS`, `ENABLE_FLOW_LOGS`
* `FLOW_LOGS_RETENTION_DAYS`, `ENV_TAG`
* Custom subnet CIDRs and the helpdesk VPC peering settings, when set

If helpdesk VPC peering is enabled but no helpdesk VPC can be resolved, the agent skips peering for this run and records a warning (Step 1.1a). Provisioning continues for everything else.

These values drive every subsequent step of the provisioning workflow.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-107e6e9b6686c8f4cbc64fb8a2c09e5d78a67f8a%2Fnetwork-step-07.png?alt=media)

### Step 8 — Phase 1: Validate

The agent runs **Phase 1 — Parse & Validate**:

* **Step 1.2** — Validates the region exists and is accessible
* **Step 1.3** — Resolves availability zone names (e.g. `us-east-1a`, `us-east-1b`) for the selected region
* **Steps 1.4–1.7** — Validates the VPC CIDR, AZ count, NAT mode and subnet mask, and computes the full CIDR layout
* **Steps 1.8–1.9** — Resolves the platform context and posts its first status update

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-eef2c8d303fbaa6c205f4f74cac3e63aeed08503%2Fnetwork-step-08.png?alt=media)

### Step 9 — Phase 2: Compute

**Phase 2 — Compute** calculates the exact subnet CIDRs and resource counts:

* **Step 2.1** — Computes public and private subnet CIDRs per AZ from the VPC CIDR block (or uses your custom CIDRs)
* **Step 2.2** — Determines NAT configuration (EIP count, NAT count, private route table count)
* **Step 2.3** — Tallies the total number of AWS resources to be created

Then **Phase 3 — Provision via CloudFormation** begins with Step 4.0 deriving the CloudFormation stack name.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-40ef3604bdac7d6e50aab226dbd3b53d3d2df599%2Fnetwork-step-09.png?alt=media)

### Step 10 — Pre-flight Checks

Before creating the stack the agent runs two pre-flight checks:

* **Step 4.1** — Checks whether the stack already exists to avoid duplicate provisioning
* **Step 4.1b** — VPC CIDR preflight: confirms no existing VPC uses the same CIDR block in the account

If both checks pass, the agent proceeds to stack creation.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-bf90e23692ef91c6f0744956e71f58d331c1e7b1%2Fnetwork-step-10.png?alt=media)

### Step 11 — CloudFormation Stack Created

* **Step 4.2** — Deploys the CloudFormation template, creating the stack
* **Step 4.3** — Starts an event-stream polling loop that tracks stack events in real time for up to 15 minutes, reporting each resource as it is created

When helpdesk VPC peering is enabled, the stack also creates the peering request, this VPC's routes to the helpdesk VPC and an inbound HTTPS rule. DuploCloud then accepts the connection and adds the matching routes on the helpdesk side.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-4a8cc53836f6692e677f00dff97a7f9984c4f06b%2Fnetwork-step-11.png?alt=media)

### Step 12 — Stack Outputs Retrieved

**Phase 5 — Finalize** begins once the stack completes:

* **Step 5.1** — Reads all stack outputs (VPC ID, subnet IDs, route table IDs, NAT gateway ID, subnet group names, etc.)

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-93600b5408c8fcc4ab0ceaae66332b09a5851bb0%2Fnetwork-step-12.png?alt=media)

### Step 13 — Runtime Details Enriched

* **Step 5.2** — Queries AWS at runtime to enrich the output with additional subnet metadata (available IPs, public IP mapping, route table associations, NAT gateway details) that CloudFormation outputs alone don't include

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-1bfdff5bd520bfedd85bbb1653dda797133cf945%2Fnetwork-step-13.png?alt=media)

### Step 14 — Output Written

* **Step 5.3** — Builds the structured `output.json` file from the enriched data, validated against the skill's output schema, for downstream provisioning steps (Plan, Cluster, Environment)
* **Step 5.4** — Posts the full results and the final status to the platform

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-341be0f17c689a6873b0adac87a22dbe3c27eb1d%2Fnetwork-step-14.png?alt=media)

### Step 15 — Provisioning Complete

The agent reports **Step 5.5 — Completion summary**. The network baseline is fully provisioned. The summary confirms:

* VPC created with the specified CIDR in the selected region
* Public and private subnets across the selected AZs
* NAT gateway with an associated Elastic IP (if enabled)
* Internet gateway, route tables, and RDS and ElastiCache subnet groups

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-917c4ae681072625e1b068bac660c512c7a19b56%2Fnetwork-step-15.png?alt=media)

## Next step

Once the network's status shows **Ready**, proceed to [Step 2: Create a Cluster](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/quick-start/provision-new/step-2-cluster.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 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/marketplace-agents/aws-extension/quick-start/provision-new/step-1-network.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.
