On a recent client connection using a route-based site-to-site VPN to an AWS peer, we were advised by support and another IBM team that only 1 connection should be configured.
Should the documentation for route-based site-to-site VPN to AWS peer be reviewed and updated to reflect the need for only 1 connection to avoid confusion?
On a recent client connection using a route-based site-to-site VPN to an AWS peer, we were advised by support and another IBM team that only 1 connection should be configured.
However the documentation for a route-based configuration guides the client to set up 2 gateways on AWS side and configure 4 connections on the IBM Cloud VPN gateway side: https://cloud.ibm.com/docs/vpc?topic=vpc-aws-config&interface=ui#aws-config-static-route-based
Should the documentation for route-based site-to-site VPN to AWS peer be reviewed and updated to reflect the need for only 1 connection to avoid confusion?