How to use VPN with a VPC hub-and-spoke architecture

Website-to-site Digital Personal Community (VPN) has been used to attach distributed networks for many years. This submit describes use a VPC VPN Gateway to attach an on-premises (enterprise) community to the IBM Cloud VPC in a transit hub-and-spoke structure:

VPN Gateway connectivity to a VPC transit hub and spoke.

Every spoke could be operated by a unique enterprise unit or group. The group can enable enterprise entry to VPC assets like Digital Service Situations operating purposes or VPC RedHat OpenShift IBM Cloud clusters. Personal enterprise entry to VPE-enabled companies, like databases, can also be attainable via the VPN gateway. With this technique, you’ll be able to benefit from the ease of use and elasticity of cloud assets and pay for simply what you want by accessing the assets securely over VPN.

The Centralize communication via a VPC Transit Hub and Spoke structure tutorial was printed just a few months in the past. The companion GitHub repository was modified to optionally assist a policy-mode VPC VPN gateway to switch the IBM Direct Hyperlink simulation.

Multi-zone area (MZR) design

The transit hub design integrates with IBM multi-zone areas (MZRs), and the VPN Gateways are zone-specific. After some cautious research, the zonal structure proven beneath was carried out. It exhibits solely two zones however could be expanded to 3:

VPN Gateway zonal connectivity.

Notes:

A VPN Gateway is related to every zone. Enterprise CIDR blocks are related to a selected cloud zone VPN Gateway. Discover the enterprise CIDR block is slender:192.168.0.0/24. The cloud CIDR block is broad, masking all the cloud (all VPCs and all zones): 10.0.0.0/8.
A VPC Deal with Prefix representing the enterprise zone is added to the transit VPC. See how phantom tackle prefix enable the spokes to route visitors to the enterprise within the tutorial.
A VPC ingress route desk is added to the transit VPC as described on this instance. It should robotically route all ingress visitors from the spokes heading to the enterprise via the VPN gateway home equipment.

Observe the steps within the companion GitHub repository within the TLDR part. When modifying the config_tf/terraform.tfvars file, be certain that the next variables are configured:

config_tf/terraform.tfvars:

enterprise_phantom_address_prefixes_in_transit = true
vpn = true
firewall = false

Additionally contemplate setting make_redis = true to permit provisioning Redis cases for the transit and spoke with related Digital Personal Endpoint Gateway connections. If configured, even the personal Redis occasion within the spoke could be accessed from the enterprise. The main points of personal DNS configuration and forwarding are coated on this part of half 2 of the tutorial.

When all the layers have been utilized, run the checks (see particular notes within the GitHub repository README.md on configuring Python if wanted). All of the checks ought to move:

python set up -r necessities.txt
pytest

A be aware on enterprise-to-transit cross-zone routing

The preliminary design labored effectively for enterprise <> spokes. The enterprise <> transit throughout the identical zone additionally labored. However further configuration is required to resolve enterprise <> transit cross-zone routing failures:

VPN Gateway cross-zone routing.

With out the extra cross-zone VPN Gateway Connections, there have been no return VPC route desk entries within the default route desk within the transit VPC to the cross-zone enterprise (see the crimson line). The VPN Gateway Connections robotically add routes to the default route desk within the transit VPC however solely within the zones containing the VPN Gateway. Within the diagram above, the employee 10.2.0.4 had no path to return to 192.168.0.4.

The additional cross-zone connections for the transit VPC zones resolved this challenge, as proven by the blue line.

Conclusions

Website-to-site VPN could be simply the know-how you must join your enterprise to the IBM Cloud VPC in a multi-zone area. Utilizing the steps described on this submit, you’ll be able to reduce the variety of VPN Gateways required to completely join the enterprise to the cloud. Benefit from the personal connectivity to VPC assets like Digital Server Situations and assets from the catalog that may be accessed via a Digital Personal Endpoint Gateway.

Study extra about IBM Cloud VPC