CLOUD
Follow this procedure to configure Confluent Cloud network peering for a cluster in AWS.
Navigate to the Cluster Settings page, click the Networking tab, and click Add Peering.
Provide the AWS Account number, AWS VPC ID, and AWS VPC CIDR for your peering connection and click Save. Your peering connection status will transition from “Pending” to “Inactive” in the Confluent Cloud web UI.
AWS Account ID of the peer VPC owner.
Unique identifier of the peer VPC. Must start with vpc-.
vpc-
AWS VPC CIDR block or subset. This must not overlap with your Confluent Cloud CIDR block or any other network peering connection VPC CIDR.
The CIDR block must be in one of the following private networks:
10.0.0.0
10.255.255.255
10/8
172.16.0.0
172.31.255.255
172.16/12
192.168.0.0
192.168.255.255
192.168/16
When the connection status is “Inactive” in the Confluent Cloud web UI, navigate to to the Amazon VPC Console and accept the peering request. You have seven days to accept the request before it expires. For more information on accepting a peering connection, see the AWS documentation.
Tip
If your request has expired, contact Confluent to resend the request. After you have accepted the peering request, the status of the peering connection will change to “Active”.
Add the new peering connection to the route table for your VPC in the the AWS Management Console. For more information about updating route tables, see the AWS documentation.
pcx-
When you are done the VPC peering status should display “Active” in the Confluent Cloud web UI.