jajera / aws-ntripcaster-ha-patterns

NTRIP caster HA patterns

BKG’s Professional NtripCaster fans GNSS streams — it does not fail over. This walkthrough keeps it reachable with AWS around it, one pattern at a time.

Start with baseline What is NtripCaster?

The idea

NTRIP carries GNSS corrections over IP. A NtripCaster sits in the middle on TCP 2101. This lab runs BKG Professional on EC2 and relay-pulls raw RTCM from a receiver IPort.

It is not clustered, not connection-migrating, and not VRS. When a host dies, in-flight TCP drops — clients reconnect. HA is AWS around that process.

Two HA patterns for NTRIP Path A: clients via Route 53 alias to one shared NLB with blue and green EC2 casters. Path B: clients via Route 53 failover to PRIMARY Auckland or SECONDARY Sydney NLB and caster. Path A / Dual-AZ L4 shared NLB / ~20-40s NTRIP :2101 Route 53 alias VIP NLB TCP health Blue / AZ-a Green / AZ-b relay pull Path B / Multi-region DNS AKL + SYD / DNS TTL 1-3+ min same VIP Route 53 failover PRIMARY AKL SECONDARY SYD both pull

Focus is caster reachability. User management / admin sync are out of scope.

1. Architecture Roles, relay-pull, why HA is bolted on 2. Prerequisites VPC, zone, tools 3. Baseline Normal relay_iport deploy 4. Dual-AZ After baseline works 5. Multi-region After dual-AZ 6. Compare Gaps and when each wins