---
updatedAt: 2026-06-25T22:42:04.000Z
agentTools:
  projectIndex: https://docs.getmontecarlo.com/llms.txt
---

# VPC Peering using CloudFormation

> ❗️ Deprecated
>
> As of January 2024, the Monte Carlo Data Collector Deployment Model has been deprecated in favor of the Agent and Object Storage Deployment models. Please see [Architecture & Deployment Options](https://docs.getmontecarlo.com/docs/platform-architecture) for more information.

For resources (e.g. Redshift, Tableau, etc.) that require peering to connect with the Data Collector, the following CloudFormation templates can be used to automate the process and help manage resources as code.

In order to peer the requester (Data Collector) and accepter (Your Resource), follow these steps -

1. Create Peering Cross Account assumable role CloudFormation stack.
2. Create Requester CloudFormation stack.
3. Create Accepter CloudFormation stack.

> 🚧 Check if the resource you want to peer with is publicly accessible
>
> Peering might not be necessary in this scenario. See [here](https://docs.getmontecarlo.com/docs/network-connectivity#ip-filtering) for more details.

> 🚧 Check for any CIDR block overlaps between the Data Collector and your resource
>
> VPC peering is not possible when the peered VPCs use overlapping CIDR blocks. If this case emerges, you may choose to use a custom CIDR block for your Monte Carlo data collector. See [here](https://docs.getmontecarlo.com/docs/deployment#advanced-options) for details.

## Step 1: Create Peering Cross Account assumable role CloudFormation stack

> 👍 This step might not be required
>
> This step is only necessary if the requester (Data Collector) and accepter (Your Resource) are not in the same AWS account.

1. Download and review the CloudFormation template.\
   <https://prod-us-east-1-mcd-data-collector.s3.amazonaws.com/peering/v1/mcd-cross-account-role.yaml>
2. Deploy the stack in the same AWS account / region as your resource. Fill in the parameter.

<Image title="Screen Shot 2021-07-15 at 2.41.09 PM.png" alt={1978} align="center" src="https://files.readme.io/c34cace-Screen_Shot_2021-07-15_at_2.41.09_PM.png">
  Parameters Wizard
</Image>

3. Retrieve the `PeeringRole` from the stack outputs. This will be used in the next step.

## Step 2: Create Requester CloudFormation stack

> ❗️
>
> If you deployed your Data Collector in an existing (customer managed) VPC with subnets that have more than one route table please reach out to your Monte Carlo representative.

1. Download and review the CloudFormation template.\
   <https://prod-us-east-1-mcd-data-collector.s3.amazonaws.com/peering/v1/mcd-requester.yaml>
2. Deploy the stack in the same AWS account / region as the requester (Data Collector). Fill in the parameters from the Data Collector and Your Resource.

<Image title="Screen Shot 2021-07-15 at 2.39.58 PM.png" alt={1984} align="center" src="https://files.readme.io/18fbdc5-Screen_Shot_2021-07-15_at_2.39.58_PM.png">
  Parameters Wizard
</Image>

3. Retrieve the `PeeringConnection` from the stack outputs. This will be used in the next step.

## Step 3: Create Accepter CloudFormation stack

> ❗️
>
> If your Resource's subnets use more than three route tables please reach out to your Monte Carlo representative.

1. Download and review the CloudFormation template.\
   <https://prod-us-east-1-mcd-data-collector.s3.amazonaws.com/peering/v1/mcd-accepter.yaml>
2. Deploy the stack in the same AWS account / region as the accepter (Your Resource). Fill in the parameters from the Data Collector and your Resource.

<Image title="Screen Shot 2022-01-26 at 1.55.11 PM.png" alt={1990} align="center" src="https://files.readme.io/cd62d60-Screen_Shot_2022-01-26_at_1.55.11_PM.png">
  Parameters Wizard
</Image>