VPC Peering FAQs

Q:  How do I create a new peering connection?
Please download the VPC Provisioning form from Request VPC Connectivity to Your Network documentation page,  and fill out the Overview and Peering tabs with the details we should use to create the new peering request. Note that VPC Peering is possible when MuleSoft is the requestor, please do not generate VPC peering requests.
Next, create a new case with MuleSoft support, and the spreadsheet attached. Please create one case per CloudHub VPC where you wish to make changes. 

Q:  What Account ID you will use to establish the Peering Request?
Requests are setup using account ID 494141260463 ​​​​​​for VPCs in the US management plane, or account ID 655988475869 for VPCs in the EU management plane.

Q:  What can I do with peering connectivity issues?
Please check the How to troubleshoot AWS VPC peering connectivity issues

Q. How much do VPC peering connections cost?
There is no charge from MuleSoft for creating VPC peering connections. However, data transfer across peering connections is charged. The cost of data transferred in and out CloudHub VPC is on MuleSoft.
AWS charges both inbound and outbound traffic to/from the customer VPC, $0.01/GB in the us-east, for example. Click VPC Peering Pricing for details.

Q. If I peer VPC A to VPC B and I peer VPC B to VPC C, does that mean VPCs A and C are peered?
No. Transitive peering relationships are not supported.

Q. Are there any bandwidth limitations for peering connections?
Bandwidth between instances in peered VPCs is no different than bandwidth between instances in the same VPC

Q. Can I peer two VPCs with matching IP address ranges?
No. Peered VPCs must have non-overlapping IP ranges.

Q. Can I create a peering connection to a VPC in a different region?
Inter-region peering is not currently supported. Both VPCs must reside in the same region. 

Q. How to enable resolution of public AWS DNS hostnames to private IP addresses when queried from the peered VPC?
Please specify this requirement in the case. We will enable DNS resolution support for the peering connection for the CloudHub VPC. Please enable DNS resolution support for the peering connection in your AWS VPC console as well. 

Q. What is the maximum number of VPC peering connections?
The peering limit is 50 (AWS docs link). Also of note, the maximum routes is 95, which you may possibly hit before the peering limit (e.g. if you are using VPNs or DirectConnect). VPN tunnels don’t count as peers, but the peering limit refers to VPC Peerings. The route limit, however, applies to all connectivity, VPN/DirectConnect peerings.
 

Q. Does CloudHub support AWS VPC endpoints / Private Links?

MuleSoft (CloudHub) does not support VPC endpoints/private link currently. So, customers won't be able to access service (private endpoint) URL from the Mulesoft VPC directly.
Instead customers can try below approach Mulesoft vpc > vpc peering > customer vpc > VPC endpoint/private endpoint. 

I do see that someone else have requested for this AWS VPC Endpoint Services in Ideas portal and you may upvote on this enhancement.