Virtual Private Cloud (VPC) peering is a method of connecting separate AWS, Google Cloud, or Azure private networks with each other. It makes it possible for the virtual machines in the different VPC's to talk to each other directly without going through the public internet.

VPC peering setup is a per project and per region setting. This means that all services created and running utilize the same VPC peering connection. If needed, you can have multiple projects that peer with different connections.

Setting it up

In order to set up a VPC peering for your Aiven project, please click on the VPC option in the left menu. Once in the Project VPC, select the Cloud you want to create the VPC for, set the IP range and finally Create VPC.

When creating a new service, you can choose whether the service will be placed in a VPC or not: The "Select Service Cloud Region" now contains a "VPC" tab containing the new Project VPC. The same functionality is available with the "Migrate" feature, allowing moving a service to / from a VPC.

The IP Range should be chosen so that it doesn't overlap with any networks you wish to peer. For example, if your own networks use the range, selecting for your Aiven project VPC makes it possible to peer the networks.

After the VPC is created it will be automatically set up by Aiven, and the status is updated in the web console's VPC view. Note that you'll need to accept a VPC peering connection request (AWS) or create a corresponding peering from your project to Aiven's (Google). See this help article for instructions of how to peer Azure virtual networks.

Did this answer your question?