Client VPN for VPC

ibmVPN gatewayibm-vpn-server

OpenVPN-compatible VPN server that remote clients dial into, authenticating by certificate, user ID or both.

Provider
ibm
Category
Edge
Properties · 3 set by this component
propertytypevaluesrequiredkind defaultthis component
activeActiveboolean—nofalseinherited
bgpboolean—nofalseinherited
clientAuthentication · component propertyenumcertificate | username | certificate-and-usernameno—inherited
highAvailability · component propertyboolean—nofalseinherited
managedboolean—nofalse▸ true
peerTypeenumsite-to-site | point-to-site | cloud-to-cloudno—▸ point-to-site
throughputMbpsinteger—no—inherited
tunnelTypeenumipsec | ssl | wireguardno—▸ ssl
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-server", component: "ibm-vpn-server" }
Other VPN gateway products · 18
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Client VPN for VPC: an OpenVPN-compatible VPN server inside a VPC that remote clients dial
# into, authenticating with certificates, with IAM user IDs, or both ("Client-to-site VPN server
# overview"). Site-to-site tunnels are VPN for VPC instead (ibm-vpn-gateway).
schemaVersion: "1"
type: "component"
id: "ibm-vpn-server"
kind: "vpn-gateway"
provider: "ibm"
docs: "https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-overview"
defaults:
  managed: true
  peerType: "point-to-site"
  tunnelType: "ssl"
properties:
  clientAuthentication:
    type: "enum"
    values: ["certificate", "username", "certificate-and-username"]
  highAvailability:
    type: "boolean"
    default: false

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