Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/multycloud/multy
Multy - Easily deploy multi cloud infrastructure. Write cloud-agnostic config deployed across multiple clouds
https://github.com/multycloud/multy
aws azure cloud go help-wanted infrastructure-as-code multi-cloud terraform
Last synced: about 1 month ago
JSON representation
Multy - Easily deploy multi cloud infrastructure. Write cloud-agnostic config deployed across multiple clouds
- Host: GitHub
- URL: https://github.com/multycloud/multy
- Owner: multycloud
- License: apache-2.0
- Created: 2022-01-08T15:17:13.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2023-02-01T14:47:35.000Z (almost 2 years ago)
- Last Synced: 2024-08-02T02:13:09.898Z (4 months ago)
- Topics: aws, azure, cloud, go, help-wanted, infrastructure-as-code, multi-cloud, terraform
- Language: Go
- Homepage: https://multy.dev
- Size: 83.8 MB
- Stars: 637
- Watchers: 13
- Forks: 34
- Open Issues: 30
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
Multy is the easiest way to deploy multi cloud infrastructure
[](https://registry.terraform.io/providers/multycloud/multy/latest/docs)
[](https://discord.gg/rgaKXY4tCZ)
[](https://github.com/multycloud/multy/actions)
# What is Multy?
**Multy** is an open-source tool that makes your infrastructure portable using a cloud-agnostic API.
You write your cloud-agnostic configuration once and Multy deploys it to the clouds you choose.
With Multy, you don't need to worry about how resources behave differently in the different clouds providers.
We abstract the nuances of each cloud so that moving your infrastructure between clouds is done by simply changing
the `cloud` parameter.
# Example
Let's try to deploy a simple virtual machine into AWS and Azure using
the [Multy Terraform Provider](https://github.com/multycloud/terraform-provider-multy)
```hcl
variable "clouds" {
type = set(string)
default = ["aws", "azure"]
}
resource "multy_virtual_network" "vn" {
for_each = var.clouds
cloud = each.key
name = "multy_vn"
cidr_block = "10.0.0.0/16"
location = "eu_west_1"
}
resource "multy_subnet" "subnet" {
for_each = var.clouds
name = "multy_subnet"
cidr_block = "10.0.10.0/24"
virtual_network_id = multy_virtual_network.vn[each.key].id
}
resource "multy_virtual_machine" "vm" {
for_each = var.clouds
name = "test_vm"
size = "general_micro"
image_reference = {
os = "ubuntu"
version = "20.04"
}
subnet_id = multy_subnet.subnet[each.key].id
cloud = each.key
location = "eu_west_1"
}
```
By using the Multy cloud-agnostic API, we can simply change the `cloud` parameter to move a resource from one cloud to
another.
If we were to deploy this using the respective cloud terraform providers, we would first need to understand how
resources such as `aws_vpc` and `azurerm_virtual_network` behave and how they differ. Then we would need to define the
same infrastructure configuration twice, one for AWS and another for Azure.
This is the equivalent terraform configuration (generated by Multy)
```hcl
// terraform: 190 lines
resource "aws_iam_instance_profile" "multy_vm_ube3b_r10" {
name = "multy_vm_ube3b_r10-vm-role"
role = aws_iam_role.multy_vm_ube3b_r10.name
provider = "aws.eu-west-1"
}
resource "aws_iam_role" "multy_vm_ube3b_r10" {
tags = { "Name" = "test_vm" }
name = "multy_vm_ube3b_r10-vm-role"
assume_role_policy = "{\"Statement\":[{\"Action\":[\"sts:AssumeRole\"],\"Effect\":\"Allow\",\"Principal\":{\"Service\":\"ec2.amazonaws.com\"}}],\"Version\":\"2012-10-17\"}"
provider = "aws.eu-west-1"
}
data "aws_ami" "multy_vm_ube3b_r10" {
owners = ["099720109477"]
most_recent = true
filter {
name = "name"
values = ["ubuntu*-20.04-amd64-server-*"]
}
filter {
name = "root-device-type"
values = ["ebs"]
}
filter {
name = "virtualization-type"
values = ["hvm"]
}
provider = "aws.eu-west-1"
}
resource "aws_instance" "multy_vm_ube3b_r10" {
tags = { "Name" = "test_vm" }
ami = data.aws_ami.multy_vm_ube3b_r10.id
instance_type = "t2.micro"
subnet_id = aws_subnet.multy_vn_ube3b_r8-1.id
iam_instance_profile = aws_iam_instance_profile.multy_vm_ube3b_r10.id
provider = "aws.eu-west-1"
}
resource "azurerm_network_interface" "multy_vm_ube3b_r9" {
resource_group_name = azurerm_resource_group.vm-nkum-rg.name
name = "test_vm"
location = "northeurope"
ip_configuration {
name = "internal"
private_ip_address_allocation = "Dynamic"
subnet_id = azurerm_subnet.multy_vn_ube3b_r7.id
primary = true
}
}
resource "random_password" "multy_vm_ube3b_r9" {
length = 16
special = true
upper = true
lower = true
number = true
}
resource "azurerm_linux_virtual_machine" "multy_vm_ube3b_r9" {
resource_group_name = azurerm_resource_group.vm-nkum-rg.name
name = "test_vm"
location = "northeurope"
size = "Standard_B1s"
network_interface_ids = [azurerm_network_interface.multy_vm_ube3b_r9.id]
os_disk {
caching = "None"
storage_account_type = "Standard_LRS"
}
admin_username = "adminuser"
admin_password = random_password.multy_vm_ube3b_r9.result
source_image_reference {
publisher = "Canonical"
offer = "0001-com-ubuntu-server-focal"
sku = "20_04-lts"
version = "latest"
}
disable_password_authentication = false
identity {
type = "SystemAssigned"
}
computer_name = "testvm"
zone = "1"
}
resource "aws_vpc" "multy_vn_ube3b_r4" {
tags = { "Name" = "multy_vn" }
cidr_block = "10.0.0.0/16"
enable_dns_hostnames = true
provider = "aws.eu-west-1"
}
resource "aws_internet_gateway" "multy_vn_ube3b_r4" {
tags = { "Name" = "multy_vn" }
vpc_id = aws_vpc.multy_vn_ube3b_r4.id
provider = "aws.eu-west-1"
}
resource "aws_default_security_group" "multy_vn_ube3b_r4" {
tags = { "Name" = "multy_vn" }
vpc_id = aws_vpc.multy_vn_ube3b_r4.id
ingress {
protocol = "-1"
from_port = 0
to_port = 0
self = true
}
egress {
protocol = "-1"
from_port = 0
to_port = 0
self = true
}
provider = "aws.eu-west-1"
}
resource "aws_vpc" "multy_vn_ube3b_r5" {
tags = { "Name" = "multy_vn" }
cidr_block = "10.0.0.0/16"
enable_dns_hostnames = true
provider = "aws.eu-west-1"
}
resource "aws_internet_gateway" "multy_vn_ube3b_r5" {
tags = { "Name" = "multy_vn" }
vpc_id = aws_vpc.multy_vn_ube3b_r5.id
provider = "aws.eu-west-1"
}
resource "aws_default_security_group" "multy_vn_ube3b_r5" {
tags = { "Name" = "multy_vn" }
vpc_id = aws_vpc.multy_vn_ube3b_r5.id
ingress {
protocol = "-1"
from_port = 0
to_port = 0
self = true
}
egress {
protocol = "-1"
from_port = 0
to_port = 0
self = true
}
provider = "aws.eu-west-1"
}
resource "azurerm_virtual_network" "multy_vn_ube3b_r6" {
resource_group_name = azurerm_resource_group.vn-nkum-rg.name
name = "multy_vn"
location = "northeurope"
address_space = ["10.0.0.0/16"]
}
resource "azurerm_route_table" "multy_vn_ube3b_r6" {
resource_group_name = azurerm_resource_group.vn-nkum-rg.name
name = "multy_vn"
location = "northeurope"
route {
name = "local"
address_prefix = "0.0.0.0/0"
next_hop_type = "VnetLocal"
}
}
resource "azurerm_subnet" "multy_vn_ube3b_r7" {
resource_group_name = azurerm_resource_group.vn-nkum-rg.name
name = "multy_subnet"
address_prefixes = ["10.0.10.0/24"]
virtual_network_name = azurerm_virtual_network.multy_vn_ube3b_r6.name
}
resource "azurerm_subnet_route_table_association" "multy_vn_ube3b_r7" {
subnet_id = azurerm_subnet.multy_vn_ube3b_r7.id
route_table_id = azurerm_route_table.multy_vn_ube3b_r6.id
}
resource "aws_subnet" "multy_vn_ube3b_r8-1" {
tags = { "Name" = "multy_subnet-1" }
cidr_block = "10.0.10.0/25"
vpc_id = aws_vpc.multy_vn_ube3b_r5.id
availability_zone = "eu-west-1a"
provider = "aws.eu-west-1"
}
resource "aws_subnet" "multy_vn_ube3b_r8-2" {
tags = { "Name" = "multy_subnet-2" }
cidr_block = "10.0.10.128/26"
vpc_id = aws_vpc.multy_vn_ube3b_r5.id
availability_zone = "eu-west-1b"
provider = "aws.eu-west-1"
}
resource "aws_subnet" "multy_vn_ube3b_r8-3" {
tags = { "Name" = "multy_subnet-3" }
cidr_block = "10.0.10.192/26"
vpc_id = aws_vpc.multy_vn_ube3b_r5.id
availability_zone = "eu-west-1c"
provider = "aws.eu-west-1"
}
resource "azurerm_resource_group" "vm-nkum-rg" {
name = "vm-nkum-rg"
location = "northeurope"
}
resource "azurerm_resource_group" "vn-nkum-rg" {
name = "vn-nkum-rg"
location = "northeurope"
}
```
With Multy, **you write once, and deploy anywhere**.
## Getting started
1. Install Terraform - [see guide](https://learn.hashicorp.com/tutorials/terraform/install-cli#install-terraform), e.g.:
- Brew (Homebrew/Mac OS): `brew tap hashicorp/tap && brew install hashicorp/tap/terraform`
- Choco (Chocolatey/Windows): `choco install terraform`
- Debian (Ubuntu/Linux):
```
sudo apt-get update && sudo apt-get install -y gnupg software-properties-common curl
curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo apt-key add -
sudo apt-add-repository "deb [arch=amd64] https://apt.releases.hashicorp.com $(lsb_release -cs) main"
sudo apt-get update && sudo apt-get install terraform
```
2. Create an account with AWS or Azure and expose
its [authentication credentials via environment variables](https://docs.multy.dev/getting-started#3-generate-access-keys)
3. Write your configuration file, for example a file named `main.tf` with the following content:
```hcl
terraform {
required_providers {
multy = {
source = "multycloud/multy"
}
}
}
provider "multy" {
aws = {} # this will look for aws credentials
}
resource "multy_virtual_network" "vn" {
cloud = "aws"
name = "multy_vn"
cidr_block = "10.0.0.0/16"
location = "eu_west_1"
}
```
4. Run `terraform init` and then `terraform apply`
5. Run `terraform destroy`
For a more detailed guide, see our official [getting started guide](https://docs.multy.dev/getting-started).
## Contributing
We love contributors! If you're interested in contributing, take a look at our [Contributing guide](./CONTRIBUTING.md)
.
Join our [discord](https://discord.gg/rgaKXY4tCZ) channel to participate in live discussions or ask for support.
Repo overview: [OVERVIEW.md](./.github/overview.md)
Terraform Provider
Repo: [https://github.com/multycloud/terraform-provider-multy](https://github.com/multycloud/terraform-provider-multy?ref=multy-gh-repo)
Discord Channel: [https://discord.gg/rgaKXY4tCZ](https://discord.gg/rgaKXY4tCZ)
## Roadmap
Have a look at our [roadmap](https://github.com/orgs/multycloud/projects/4) to know the latest features released and
what we're focusing on short and long term.
You can also vote for a specific feature you want or participate in
the [discussions](https://github.com/multycloud/multy/discussions).
## FAQ
### Why build with Multy?
Multy was born after realising how difficult it is to run the same infrastructure across multiple clouds. While
providers such as AWS and Azure share the same set of core services, the small differences in how each service works
make it difficult to configure your infrastructure to run in the same way.
This is the problem that Multy aims to tackle. We created a single interface to deploy resources that have the same
behaviour regardless of the cloud provider.
### Can I use Multy for free?
Multy is available as a free and open-source tool, so you can download it directly and run it locally.
We also offer a managed solution that hosts the server for you. Managed Multy is currently offered as a free service.
You can request an API key by visiting our [website](https://multy.dev).
### Why not use the cloud specific Terraform providers?
While Terraform and its providers are great for deploying any resource into any cloud, it puts all the burden on the
infrastructure teams when it comes to understanding each provider and defining the resources. This flexibility can be
seen as an advantage, however, when it comes to multi-cloud, this considerably slows down teams that are looking to move
fast with deployments.
By abstracting the common resources across major cloud providers, users are able to deploy the same resources on AWS and
Azure without re-writing any infrastructure code.
### I want to use cloud managed resources (i.e. Amazon S3 / Azure Key Vault), is Multy for me?
Absolutely! The goal with Multy is to allow you to leverage cloud managed services and remain free to move your
infrastructure.
Not every resource will be supported, but we aim to support the most popular managed resources such as managed
databases, object storage and vault.
Let us know what services you would like to be supported by creating an Issue on
the [Issues section](https://github.com/multycloud/multy/issues).
### Why should I be locked in to Multy?
Multy is an open-source tool that can be run locally and free. If at some point you want to move off Multy, you can
export your infrastructure configuration as Terraform and use it independently.
## License
This repository is available under [Apache 2.0](./LICENSE).