Files
smom-dbis-138/terraform/phases/phase1/connectivity
defiQUG 1fb7266469 Add Oracle Aggregator and CCIP Integration
- Introduced Aggregator.sol for Chainlink-compatible oracle functionality, including round-based updates and access control.
- Added OracleWithCCIP.sol to extend Aggregator with CCIP cross-chain messaging capabilities.
- Created .gitmodules to include OpenZeppelin contracts as a submodule.
- Developed a comprehensive deployment guide in NEXT_STEPS_COMPLETE_GUIDE.md for Phase 2 and smart contract deployment.
- Implemented Vite configuration for the orchestration portal, supporting both Vue and React frameworks.
- Added server-side logic for the Multi-Cloud Orchestration Portal, including API endpoints for environment management and monitoring.
- Created scripts for resource import and usage validation across non-US regions.
- Added tests for CCIP error handling and integration to ensure robust functionality.
- Included various new files and directories for the orchestration portal and deployment scripts.
2025-12-12 14:57:48 -08:00
..

Cross-Region Connectivity Options

This directory contains Terraform configurations for cross-region connectivity between West Europe (Nginx proxy) and US regions (backend VMs).

Options

  • File: vpn-gateway.tf
  • Cost: ~$150/month for VpnGw1
  • Setup Time: 1-2 hours
  • Pros:
    • Native Azure solution
    • Secure (IPsec)
    • Good performance
  • Cons:
    • Requires VPN Gateway in each region (or site-to-site VPN)
    • Higher cost than Cloudflare Tunnel

Option B: Cloudflare Tunnel on Backend VMs

  • File: scripts/setup-cloudflare-tunnel-backend.sh (already exists)
  • Cost: Free (Cloudflare Tunnel)
  • Setup Time: 30 minutes
  • Pros:
    • No VPN infrastructure needed
    • Free
    • Quick setup
  • Cons:
    • Adds latency
    • Requires Cloudflare Tunnel on each VM
  • File: Not yet implemented
  • Cost: ~$0.01/GB data transfer
  • Setup Time: 2-3 hours
  • Pros:
    • Azure-native
    • Secure
    • Good for production
  • Cons:
    • More complex setup
    • Requires Private Link services

Recommendation

For Phase 1, use Option B (Cloudflare Tunnel) for quick setup, then migrate to Option A (VPN Gateway) for production.

Usage

VPN Gateway Setup

cd terraform/phases/phase1/connectivity
terraform init
terraform plan
terraform apply

Cloudflare Tunnel Setup

# On each backend VM (via VPN/Bastion)
ssh besuadmin@<backend-vm-ip>
/tmp/setup-cloudflare-tunnel-backend.sh <vm-name> <region>