isopod/chasm repository overview

⁠Chasm

⁠Description

Chasm⁠ is a set of tools under Isopod⁠, an open-source project owned by Stateless, Inc.⁠ Chasms are what many businesses run into when trying to find the skill-sets and knowledge to navigate between the different cloud provider's environments. This can include APIs, tools, languages, networking architectures, and even having visibility into what subnets you might have in each cloud environment. When what you really want is to be able to get your data from one place to the another that you need... crossing that chasm.

The process of creating IPsec⁠ tunnels between virtual private clouds⁠ (VPCs) is different in each Cloud Service Provider (CSP), and it can be difficult to automate due to how IP addressing is handled (particularly for inter-cloud connectivity), eventual consistency in the standard CSPs APIs, and some dizzying circular dependencies to navigate through.

Enter Chasm, a tool for bridging the gaps between the clouds for you.

⁠Core functions

• Report all your VPCs and subnets from your CSPs.
• Create a mesh IPsec⁠ network out of the cloud subnets you select from these CSPs.

⁠Network designs supported

• Inter-cloud meshing: meshing subnets between two or more distinct clouds i.e. AWS and GCP.

• Mix of inter and intra-cloud Meshing: meshing subnets between two or more distinct clouds, and more than one subnet within same CSP, where same CSP is under a single account.

⁠Known limitations

No NAT: There is no built in NAT, meaning we can't mesh subnets with overlapping CIDRS.

• Multi-account, single cloud meshing: We currently do not support situations where you have more than one account associated to a single CSP and want to mesh two or more subnets that are in different CSP accounts (i.e. if you have two AWS accounts with a subnet in account A, and a subnet in account B, these tools do not currently support connectivity between them).

• Azure cross-subscription meshing: You cannot connect two or more Azure subnets across Azure subscriptions.

• AWS cross-region meshing: You cannot connect two or more AWS subnets across AWS regions.

• GCP cross-project meshing: You cannot mesh together two VPCs across GCP projects.

⁠Supported clouds

• Amazon Web Services (AWS)⁠
• Google Cloud Platform (GCP)⁠
• Microsoft Azure Cloud Platform⁠