> For the complete documentation index, see [llms.txt](https://docs.finopscenter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finopscenter.com/technical-documentation/adding-to-vpc.md).

# Adding to VPC

FinOps Center S3, Lambda, and DynamoDB components like any other application via VPC Endpoints. 

New VPC

* 1 VPC, e.g. `10.0.0.0/16`
* At least **2 public** and **2 private** subnets across 2 AZs
* Internet Gateway attached
* NAT Gateway(s) in public subnets
* Route tables:
  * Public subnets → `0.0.0.0/0` via IGW
  * Private subnets → `0.0.0.0/0` via NAT

Attach FinOps Center Lambdas to the VPC

For each Lambda that should live “inside the VPC”:

 IAM for VPC attachment

Add the managed policy **`AWSLambdaVPCAccessExecutionRole`** to the Lambda execution role so Lambda can create Hyperplane ENIs

Attach Data

* **S3 Gateway** – for CUR 2.0, Cost Optimization Hub exports, Athena query results
* **Interface endpoints** (AWS PrivateLink) for:
  * `com.amazonaws.<region>.dynamodb`
  * `...sts`
  * `...logs` (if you want private delivery to CloudWatch Logs)
  * `...secretsmanager` / `...ssm` / `...lambda` as needed [AWS Documentation+1](https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances-networking.html?utm_source=chatgpt.com)

Attach security groups that allow inbound from `sg-finopscenter-lambda` (or ECS SG) on 443.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.finopscenter.com/technical-documentation/adding-to-vpc.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.