Set Up a Zapier VPC Peering Connection

This guide explains how to connect your AWS Virtual Private Cloud (VPC) to Zapier using a VPC peering connection so that your private resources can communicate securely with the Zapier platform.

By following these steps, you will prepare your AWS environment, exchange key connection details with support, and validate that your private services can be accessed from Zapier without exposing them to the public internet.

Before You Start With Zapier VPC Peering

Before you request a VPC peering connection with Zapier, make sure your AWS environment is ready and that you have the correct information available.

Information You Need for Zapier VPC Setup

Collect the following details from your AWS account:

• AWS account ID
• VPC ID for the VPC that will connect to Zapier
• VPC region where your VPC is hosted
• VPC CIDR block used by your network

You will provide this information to the support team so the Zapier side of the VPC peering connection can be created correctly.

Check CIDR Compatibility for Zapier Peering

Zapier uses CIDR ranges in its own VPC. Your VPC must not overlap with those ranges or the peering connection will not work as expected.

The Zapier VPC uses three CIDR blocks:

• 172.31.0.0/16
• 172.30.0.0/16
• 10.0.0.0/8

Make sure the CIDR block of your VPC does not overlap with any of these. If it does, create or select a different VPC with a non-overlapping CIDR block before proceeding.

Requesting a Zapier VPC Peering Connection

Once you have confirmed that your CIDR range is compatible, you can request a peering connection with Zapier.

How to Request VPC Peering With Zapier

To request the connection, contact the support team and include:

• Your AWS account ID
• Your VPC ID
• The AWS region for that VPC
• The VPC CIDR block

After your request is approved, the Zapier team creates a peering connection from their AWS account to yours. You will receive the details you need to finish the configuration in your own AWS console.

You can reference the original instructions in the official help documentation at this Zapier VPC peering article.

Accepting the Zapier VPC Peering Request

When Zapier initiates the VPC peering connection, a pending request appears in your AWS account. You must accept it before traffic can flow.

Steps to Accept the Zapier VPC Request in AWS

1. Sign in to the AWS Management Console.
2. Go to VPC in the AWS services list.
3. In the left navigation, select Peering Connections.
4. Locate the peering request sent from the Zapier AWS account.
5. Select the request and click Actions > Accept Request.
6. Confirm the acceptance.

After you accept the request, the peering connection status should change from pending-acceptance to active.

Configuring Route Tables for Zapier Connectivity

The VPC peering connection is only part of the setup. You must also update your route tables so that traffic can flow between your VPC and the Zapier VPC.

Add Routes for Zapier VPC Peering

In each relevant route table, add routes that point traffic for the Zapier CIDR ranges through the peering connection.

1. Open the AWS VPC console.
2. Choose Route Tables from the navigation pane.
3. Select the route table associated with the subnets that host the resources you want to expose to Zapier.
4. Go to the Routes tab and click Edit routes.
5. Add a new route where:
   • Destination: a Zapier VPC CIDR block provided by support.
   • Target: your VPC peering connection identifier.
6. Save the updated routes.

Repeat this for each route table that should allow access for Zapier traffic.

Security Group and Firewall Settings for Zapier

In addition to routes, security rules must permit inbound and outbound traffic between your private resources and the Zapier VPC.

Update Security Groups for Zapier Access

Review the security groups that protect the instances or services to be used with Zapier. For each relevant security group:

• Allow inbound traffic from the specific Zapier CIDR blocks on the ports your service requires (for example, HTTP or HTTPS).
• Confirm that outbound rules allow responses back to the Zapier CIDR ranges.

These changes ensure that private endpoints, databases, or APIs are reachable only from the Zapier VPC, not from the public internet.

Network ACL Considerations for Zapier Traffic

If your subnets use network ACLs, verify that they also allow the traffic required for Zapier connectivity:

• Check inbound ACL rules for entries that permit traffic from the Zapier CIDR ranges.
• Check outbound ACL rules for traffic headed back to the Zapier ranges.

Both security groups and network ACLs must be aligned to avoid blocked requests from the Zapier infrastructure.

Validating Your Zapier VPC Peering Connection

After you have accepted the peering connection, updated the route tables, and configured your security rules, confirm that everything works as expected.

How to Test Zapier Connectivity

Use one of the following approaches to test the connection:

• From an instance in your VPC, attempt to reach a service that Zapier will access and verify logs or metrics to confirm traffic is flowing.
• Coordinate with support to run a test from Zapier to your private endpoint and confirm that requests are received.

If requests fail, review:

• The peering connection status in AWS (must be active).
• The route tables for entries pointing to the Zapier CIDR ranges.
• Security groups and network ACLs for blocked ports or IP ranges.

Best Practices for Managing Zapier VPC Peering

Once your VPC is connected to Zapier, follow these best practices to keep the configuration secure and maintainable.

• Limit access to only the subnets and services that must communicate with Zapier.
• Restrict allowed ports and protocols to the minimum necessary for your workflows.
• Monitor logs for unusual traffic patterns coming from or going to the Zapier CIDR ranges.
• Periodically review routes and security rules when your infrastructure changes.

For broader integration strategy and automation architecture planning, you can also consult specialist resources such as Consultevo for help with designing scalable, secure setups.

Troubleshooting Zapier VPC Peering Issues

If you run into problems using Zapier with your private resources, focus on a few common configuration areas.

Common Issues With Zapier VPC Peering

• Overlapping CIDR ranges: If your VPC overlaps with the Zapier CIDR, the connection will not route correctly.
• Missing routes: If no route exists for the Zapier ranges, traffic will never reach your instances.
• Security rules too strict: Security groups or ACLs may be blocking requests from the Zapier VPC.
• Incorrect ports: The services you want Zapier to call might listen on ports that are not opened in your rules.

Correcting these issues typically restores connectivity between your AWS resources and the Zapier environment.

By following this step-by-step process—preparing your VPC, requesting the connection, updating routing and security, and validating the setup—you can integrate your private infrastructure with Zapier in a secure and controlled way.

Need Help With Zapier?

Work with ConsultEvo — a

Zapier Certified Solution Partner

helping teams build reliable, scalable automations that actually move the business forward.

Get Zapier Help