IBM Cloud VPN for VPC

ibmVPN gatewayibm-vpn-gateway

IPsec site-to-site tunnel from a VPC to an on-premises network or another VPC, route-based or policy-based.

Provider
ibm
Category
Edge
Properties · 3 set by this component
propertytypevaluesrequiredkind defaultthis component
activeActiveboolean—nofalseinherited
bgpboolean—nofalseinherited
haMode · component propertyenumactive-backup | active-active | active-standbyno—inherited
managedboolean—nofalse▸ true
mode · component propertyenumroute-based | policy-basedno—inherited
peerTypeenumsite-to-site | point-to-site | cloud-to-cloudno—▸ site-to-site
throughputMbpsinteger—no—inherited
tunnelTypeenumipsec | ssl | wireguardno—▸ ipsec
Rules that apply · 0

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

No rule reads this kind yet. That is a gap, not a guarantee.
Use it in a design
nodes:
  - { id: "vpn-gateway", component: "ibm-vpn-gateway" }
Other VPN gateway products · 18
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# IBM Cloud VPN for VPC: an "IPsec site-to-site tunnel between your VPC and your on-premises
# private network or another VPC", in route-based mode (static routes or BGP-learned routes,
# active-backup or active-active) or policy-based mode (active-standby, no BGP)
# ("About site-to-site VPN gateways"). Neither the mode nor a throughput figure is documented as a
# default, so only the peer and tunnel type are set.
schemaVersion: "1"
type: "component"
id: "ibm-vpn-gateway"
kind: "vpn-gateway"
provider: "ibm"
docs: "https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpn"
defaults:
  managed: true
  peerType: "site-to-site"
  tunnelType: "ipsec"
properties:
  mode:
    type: "enum"
    values: ["route-based", "policy-based"]
  haMode:
    type: "enum"
    values: ["active-backup", "active-active", "active-standby"]

The same page as markdown, for an agent: /catalogue/components/ibm-vpn-gateway.md