Summary
This example will build Aviatrix Transit between OCI and Azure including all of the infrastructure in both clouds.
Aviatrix automates the workflow while providing ongoing visibility, control, and the means to do this with multiple accounts and multicloud.
- VCNs, VNETs, Transit Gateway, Spoke Gateways with connected transit
Prerequisites
- Aviatrix Controller can be launched in from OCI Marketplace in a few minutes instructions here.
- OCI Access Account onboarded to Controller instructions here.
- Azure Access Account onboarded to Controller instructions here.
VMStandard2.2
shapes available in OCI region(s), check limitsStandard_B1s
available in Azure region(s)- The region defaults are
us-ashburn-1
andEast US
you can modify them by adding your own interraform.tfvars
Getting Started
- Modify
terraform.tfvars
with values for your Controller details specifying thecontroller ip, username, password, oci_account_name, azure_acccount_name
terraform init
terraform plan
terraform apply
- To destroy
terraform destroy
What to expect
The Terraform automation will take ~20 minutes, you can monitor progress in the Aviatrix Controller, OCI Console, Azure Portal, or the terminal.
When complete your OCI spoke VCN and Azure VCN will be able to communicate through Aviatrix Transit.
Enjoy!