> 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/use-cases/creating-an-infrastructure-and-plan-for-aws/add-vpc-endpoints.md).

# Add VPC endpoints

Securely access AWS Services using VPC endpoints

An AWS [VPC endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/concepts.html?ref=wellarchitected) creates a private connection to supported AWS services and VPC endpoint services powered by AWS PrivateLink. Amazon VPC instances do not require public IP addresses to communicate with the resources of the service. Traffic between an Amazon VPC and a service does not leave the Amazon network.

VPC endpoints are virtual devices. They are horizontally scaled, redundant, and highly available Amazon VPC components that allow communication between instances in an Amazon VPC and services without imposing availability risks or bandwidth constraints on network traffic. There are two types of VPC endpoints, [Interface Endpoints](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html), and [Gateway Endpoints](https://docs.aws.amazon.com/vpc/latest/privatelink/gateway-endpoints.html).

DuploCloud allows you to specify predefined AWS endpoints for your Infrastructure in the DuploCloud Portal.

## Adding VPC endpoints to a Duplocloud Infrastructure

1. In the DuploCloud Portal, navigate to **Administrator** -> **Infrastructure**. The **Infrastructure** page displays.
2. Select the Infrastructure to which you want to add VPC endpoints.
3. Click the **Endpoints** tab.
4. Click **Add**. The **Infra - Create VPC Endpoints** pane displays.<br>

   <div align="left"><figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FZtAJOPDdk6vt2IADabn9%2FAWS_VPC_End1.png?alt=media&amp;token=c7653d19-f80d-4b5c-b2a8-1b0b2a3f6421" alt=""><figcaption><p><strong>Infra - Create VPC Endpoints</strong> pane displaying avaliable VPC Endpoints</p></figcaption></figure></div>
5. From the **VPC Endpoint Service** list box, select the endpoint service you want to add.
6. Click **Create**. In the **Endpoints** tab, the **VPC Endpoint ID** of your selected service displays.<br>

   <div align="left"><figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FdAe9s0IdfyX7d1OiSmbr%2FAWS_VPC_End2.png?alt=media&amp;token=2a20ce56-04d9-46a9-9b0b-72fe937ffcce" alt=""><figcaption><p><strong>Infrastructure</strong> page with <strong>Endpoints</strong> tab</p></figcaption></figure></div>


---

# 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/use-cases/creating-an-infrastructure-and-plan-for-aws/add-vpc-endpoints.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.
