Interconnection

Fugoku Interconnection provides private connectivity between your infrastructure and external networks. Choose from VPC peering, IPsec VPN, or dedicated cross-connects with BGP routing.

Access interconnection management at: console.fugoku.com/interconnection

Connection Types

All interconnection traffic — peering, VPN, Direct Connect — is included in your plan with zero egress fees.

VPC Peering

Private connectivity between your Fugoku VPCs or projects. No internet traversal.

Features

• Private RFC1918 addressing — No public IPs needed
• Non-transitive — A↔B and B↔C doesn't imply A↔C (use hub-and-spoke)
• Cross-project — Peer between projects in same organization
• Cross-region — Peer across Fugoku regions
• Instant provisioning — No hardware, pure software-defined

Create Peering

Console:

1. Navigate to Interconnection → Peerings
2. Click Create Peering
3. Select:
   • Local Network: Your VPC
   • Remote Network: Target VPC (same org or external)
   • Routing: BGP (recommended) or static
4. Click Create — Active in seconds

CLI:

fugoku peering create \
  --local-network vpc-prod \
  --remote-network vpc-staging \
  --routing bgp

Peering Constraints

• No transitive routing — A↔B and B↔C ≠ A↔C
• Non-overlapping CIDRs — Local and remote CIDRs must not overlap
• Max 128 peerings per VPC (soft limit, adjustable)

IPsec VPN

Standards-based site-to-site VPN for hybrid cloud and on-premises connectivity.

Features

• IKEv2 with AES-256-GCM encryption
• BGP or static routing
• NAT traversal (NAT-T) supported
• Dead Peer Detection (DPD) for fast failover
• Multi-SA for traffic segmentation
• Perfect Forward Secrecy (PFS) Group 14/19/20

Create VPN

Console:

1. Navigate to Interconnection → VPN
2. Click Create VPN
3. Configure:
   • Name: vpn-to-onprem-dc1
   • Remote Gateway: Your on-prem public IP
   • Remote CIDR: 10.0.0.0/16 (your on-prem network)
   • Local CIDR: 10.10.0.0/16 (your Fugoku VPC)
   • PSK: Auto-generated or custom
   • IKE Version: v2 (recommended)
   • Encryption: AES-256-GCM
   • DH Group: 14 (2048-bit), 19 (256-bit ECP), 20 (384-bit ECP)
   • Routing: BGP (recommended) or static routes
4. Click Create — Tunnel establishes in ~30 seconds

CLI:

fugoku vpn create \
  --name vpn-to-onprem \
  --remote-gateway 203.0.113.50 \
  --remote-cidr 10.0.0.0/16 \
  --local-cidr 10.10.0.0/16 \
  --psk auto \
  --routing bgp

VPN Configuration on Your Side

StrongSwan (Linux):

conn fugoku-vpn
    left=%defaultroute
    leftid=@your-domain.com
    leftsubnet=10.0.0.0/16
    right=fugoku-vpn-gateway
    rightid=@fugoku.com
    rightsubnet=10.10.0.0/16
    ike=aes256gcm16-prfsha384-ecp384!
    esp=aes256gcm16-ecp384!
    ikev2=insist
    dpdaction=restart
    dpddelay=30
    dpdtimeout=120
    auto=start

Cisco ASA:

crypto ikev2 policy 10
 encryption aes-256-gcm
 integrity sha384
 group 19
 lifetime 86400
crypto ipsec profile fugoku-vpn
 set ikev2 ipsec-proposal AES256-GCM

VPN Monitoring

# Check tunnel status
fugoku vpn status vpn-to-onprem

# View tunnel metrics
fugoku vpn metrics vpn-to-onprem --period 1h

Direct Connect

Dedicated physical cross-connects at Fugoku PoPs for highest performance and compliance.

Specifications

Features

• Your ASN — Full BGP with your autonomous system number
• BGP Communities — Route filtering, MED, local preference, AS-path prepend
• Route Reflectors — For scale (100+ prefixes)
• BFD — Sub-second failure detection
• ECMP — Equal-cost multi-path for load balancing
• Graceful Restart — Non-disruptive maintenance
• MACsec — Optional link-layer encryption (10/100G)

Ordering Process

1. Submit Request — Console → Interconnection → Direct Connect → Request
2. Port Allocation — Fugoku provisions port at selected PoP
3. Cross-Connect — Your carrier patches to Fugoku patch panel
4. BGP Session — Configure BGP with your ASN and Fugoku ASN (65001)
5. Validation — Bidirectional traffic test
6. Go Live — Traffic flows

CLI (after provisioning):

fugoku direct-connect create \
  --name dc-ashburn-primary \
  --pop ashburn-1 \
  --speed 10g \
  --your-asn 65000 \
  --fugoku-asn 65001 \
  --bgp-password your-bgp-password

BGP Configuration

Your Router (Cisco):

router bgp 65000
 neighbor 169.254.0.1 remote-as 65001
 neighbor 169.254.0.1 password your-bgp-password
 neighbor 169.254.0.1 timers 30 90
 neighbor 169.254.0.1 fall-over bfd
 address-family ipv4
  neighbor 169.254.0.1 activate
  neighbor 169.254.0.1 route-map FUGOKU_OUT out
  neighbor 169.254.0.1 route-map FUGOKU_IN in
 exit-address-family
!
route-map FUGOKU_OUT permit 10
 match ip address prefix-list YOUR_PREFIXES
!
route-map FUGOKU_IN permit 10

Redundancy

• Dual cross-connects — Separate fibers, diverse paths
• BFD — Sub-second failure detection
• ECMP — Equal-cost load balancing across links
• Graceful Restart — Non-disruptive BGP restart
• 99.99% SLA — On Direct Connect with dual cross-connects

Routing Options

BGP Best Practices

• Use private ASN (64512-65534) for VPN peering
• Advertise only your prefixes — Use prefix-lists
• Set MED/LOCAL_PREF for traffic engineering
• Use BGP communities for route tagging
• Enable BFD for sub-second failover
• Enable Graceful Restart for non-disruptive updates

Interconnection Dashboard

Console: Interconnection Page

• Peerings tab — List, create, delete VPC peerings
• VPN tab — List, create, monitor, delete VPNs
• Direct Connect tab — List, order, monitor cross-connects
• Metrics — Bandwidth, latency, packet loss per connection

Metrics Available

CLI Monitoring

# List all interconnections
fugoku interconnection list

# View specific connection metrics
fugoku interconnection metrics peering-abc --period 1h
fugoku interconnection metrics vpn-xyz --period 24h
fugoku interconnection metrics dc-ashburn --period 1h

Security

Compliance

• SOC 2 — All interconnection types
• HIPAA — VPN (AES-256), Direct Connect (MACsec)
• PCI DSS — VPN, Direct Connect
• GDPR — Data never leaves your control plane

Troubleshooting

VPN Won't Connect

1. Verify PSK — Match exactly on both sides
2. Check IKE version — Both must use IKEv2
3. Verify CIDRs — Local/remote must match exactly
4. Check NAT-T — Enable if behind NAT
5. Check DPD — Both sides must agree on interval
6. Firewall — UDP 500, UDP 4500, ESP (protocol 50)

BGP Not Establishing

1. ASN mismatch — Verify both ASNs
2. BGP password — Must match exactly
3. TTL — Must be 255 (or multihop configured)
4. Prefix-lists — Ensure your prefixes are allowed
5. Check logs — fugoku interconnection logs dc-ashburn

Peering Not Working

1. CIDR overlap — Must not overlap
2. Project permissions — Both projects in same org
3. Route tables — Ensure routes propagated

CLI Reference

# Peering
fugoku peering create --local-network vpc-a --remote-network vpc-b --routing bgp
fugoku peering list
fugoku peering delete peering-abc --confirm

# VPN
fugoku vpn create --name vpn-dc1 --remote-gateway 203.0.113.10 --remote-cidr 10.0.0.0/16 --local-cidr 10.10.0.0/16 --routing bgp
fugoku vpn list
fugoku vpn status vpn-dc1
fugoku vpn delete vpn-dc1 --confirm

# Direct Connect
fugoku direct-connect list
fugoku direct-connect metrics dc-ashburn --period 1h

# All interconnections
fugoku interconnection list

Pricing

All interconnection data transfer is included — zero egress fees.

Getting Help

• Documentation: docs.fugoku.com/interconnection
• Support: support@fugoku.com
• Status: status.fugoku.com
• Network Engineering: network@fugoku.com

Next Steps:

• Create a VPC Peering
• Set up IPsec VPN
• Request Direct Connect
• Explore Private Networks for VLANs
• Configure Firewalls for edge security