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

# Provision New Infrastructure

Build new AWS infrastructure from scratch — Network, Cluster, Plan, Environment, Workloads, and Databases.

This guide walks through creating a complete AWS environment from scratch using the Infrastructure Agent — from the VPC network up to running workloads and managed databases.

## What you will build

By the end of this guide, you will have:

* A **Network Baseline** — a VPC with public and private subnets across multiple availability zones
* A **Cluster Baseline** — an EKS cluster running inside that network
* A **Plan** — an account-level catalog of hosted zones, certificates, and AMIs
* An **Environment** — a deployment boundary inside the cluster with dedicated IAM and security group isolation
* **Workloads** — a running application deployed into the Environment
* **Databases** — a managed RDS or ElastiCache instance

## Steps

{% stepper %}
{% step %}

### [Create a Network](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/quick-start/provision-new/step-1-network.md)

Provision a VPC with public and private subnets across multiple availability zones, NAT gateways, and RDS/ElastiCache subnet groups.
{% endstep %}

{% step %}

### [Create a Cluster](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/quick-start/provision-new/step-2-cluster.md)

Provision an EKS cluster inside your Network Baseline. Choose Standard or Auto Mode depending on your workload requirements.
{% endstep %}

{% step %}

### [Create a Plan](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/quick-start/provision-new/step-3-plan.md)

Create an account-level catalog of Route 53 hosted zones, ACM certificates, and AMIs that your Environments will reference.
{% endstep %}

{% step %}

### [Create an Environment](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/quick-start/provision-new/step-4-environment.md)

Group your Plan and Resource Groups in an Environment, then create a Resource Group that provisions its own security groups, IAM role and KMS key on your network and cluster.
{% endstep %}

{% step %}

### [Deploy Workloads](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/quick-start/provision-new/step-5-workloads.md)

Create a Namespace and deploy a containerized application into your Environment. Optionally attach a load balancer to expose the application externally.
{% endstep %}

{% step %}

### [Add Databases](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/quick-start/provision-new/step-6-databases.md)

Provision a managed RDS or ElastiCache instance into the private subnets of your Network Baseline. Databases are immediately accessible from workloads in the same Environment.
{% endstep %}
{% endstepper %}

## Prerequisites

* DuploCloud is installed and running. See [Installation](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/installation.md).
* An AWS Provider with write access to your AWS account is connected. See [Integrating Providers](https://docs.duplocloud.com/docs/concepts/providers/integrating-providers.md).
* A Workspace has been created with the AWS Provider scope attached.


---

# 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.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.
