Virtual Gateway
Entry and exit point on the OUTSCALE side of a site-to-site VPN, attached to one Net.
- Provider
- outscale
- Kind
- VPN gateway
- Category
- Edge
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| activeActive | boolean | — | no | false | ▸ false |
| bgp | boolean | — | no | false | inherited |
| clientGatewaysPerVirtualGateway | integer | — | no | 5 | inherited |
| managed | boolean | — | no | false | ▸ true |
| peerType | enum | site-to-site | point-to-site | cloud-to-cloud | no | — | ▸ site-to-site |
| throughputMbps | integer | — | no | — | inherited |
| tunnelInitiatedByClientGateway | boolean | — | no | true | inherited |
| tunnelType | enum | ipsec | ssl | wireguard | no | — | ▸ ipsec |
| virtualGatewaysPerNet | integer | — | no | 1 | inherited |
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.
nodes:
- { id: "virtual-gateway", component: "outscale-virtual-gateway" }VPN Gatewayalibaba-vpn-gatewayAWS Client VPNaws-client-vpnAWS Site-to-Site VPNaws-site-to-site-vpnAzure VPN Gatewayazure-vpn-gatewayNetBirdnetbirdOpenVPNopenvpnstrongSwanstrongswanSubmarinersubmarinerTailscaletailscaleGeneric VPN gatewayvpn-gatewayWireGuardwireguardZeroTierzerotierCloud VPNgoogle-cloud-vpnIBM Cloud VPN for VPCibm-vpn-gatewayClient VPN for VPCibm-vpn-serverSite-to-Site VPNoci-site-to-site-vpnNeutron VPNaaSopenstack-neutron-vpnaasClient Gatewayoutscale-client-gateway
# yaml-language-server: $schema=../../schema/component.schema.json # OUTSCALE virtual gateway: the entry and exit point on the OUTSCALE side of a site-to-site # VPN, attached to a Net ("About Virtual Gateways"). That page states one virtual gateway per # Net and up to five client gateways connected to it; "About VPN Connections" states the # tunnel is encrypted with IPsec, stays down until the client gateway sends traffic, and that # redundancy comes from creating several VPN connections. schemaVersion: "1" type: "component" id: "outscale-virtual-gateway" kind: "vpn-gateway" provider: "outscale" docs: "https://docs.outscale.com/en/userguide/About-Virtual-Gateways.html" defaults: managed: true peerType: "site-to-site" tunnelType: "ipsec" activeActive: false properties: virtualGatewaysPerNet: type: "integer" default: 1 clientGatewaysPerVirtualGateway: type: "integer" default: 5 tunnelInitiatedByClientGateway: type: "boolean" default: true