VPN concept #159
yunkon-kim
started this conversation in
Show and tell
VPN concept
#159
Replies: 1 comment
-
Thanks for this informative discussion! :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, forks 👋
I open this discussion to share the current VPN concept, and it will continue to improve.
Introduction to AWS-to-site VPN
First, I chose AWS, which has the highest market share. The concept of AWS-to-site VPN refers to creating a site-to-site VPN between AWS and another CSP.
Note: The site refers to VPC, VPC network, and Virtual Network. We refer to this as a "vNet" in CB-Tumblebug.
AWS-to-site VPN currently supports MS Azure, GCP, Alibaba, Tencent, IBM. Depending on the characteristics of CSP, dynamic routing and static routing are supported.
Objectives
Terrarium can help you configure a site-to-site VPN, like ordering a combo at a fast food restaurant. We’ll handle what’s under the hood to ensure maturity and stability.
Actually, configuring a VPN is very complicated... 😟
This is because each CSP has different concepts/characteristics for VPN, and VPNs must be configured between CSPs.
The following figure is an example illustrating this, showing the various resources, information, and dependencies required to configure a VPN between AWS and Azure. In particular, dependencies affecting different CSPs make VPN control mechanisms more complex.
But don’t worry, Terrarium can handle this challenge. 😎
Beta Was this translation helpful? Give feedback.
All reactions