https://docs.trustgrid.io/tutorials/deployments/deploy-aws/Recent content in Deploy a Trustgrid Node in AWS onHugoenhttps://docs.trustgrid.io/tutorials/deployments/deploy-aws/wireguard-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://docs.trustgrid.io/tutorials/deployments/deploy-aws/wireguard-cluster/This tutorial covers fronting a clustered Trustgrid node in AWS with a Network Load Balancer (NLB) so that Wireguard clients connect to a single stable endpoint and the NLB directs traffic to the active cluster member. Only the active member of a Trustgrid cluster responds healthy to the load balancer health check, so the NLB always forwards traffic to the active node. Prerequisites A two-member Trustgrid HA cluster deployed in AWS.https://docs.trustgrid.io/tutorials/deployments/deploy-aws/ip-failover/Mon, 01 Jan 0001 00:00:00 +0000https://docs.trustgrid.io/tutorials/deployments/deploy-aws/ip-failover/This tutorial covers the cluster IP failover mechanism for AWS-hosted Trustgrid clusters. The active cluster member claims a configured IP as a secondary private IP on its data ENI via ec2:AssignPrivateIpAddresses (with AllowReassignment=true). On failover, the standby promotes itself and reclaims the same secondary IP on its own ENI — no AWS route-table updates required. For L3 overlay route failover instead, see Configure HA Gateway Cluster in AWS. How it works The cluster IP is an unused private IP in the data-interface subnet.https://docs.trustgrid.io/tutorials/deployments/deploy-aws/route-failover/Mon, 01 Jan 0001 00:00:00 +0000https://docs.trustgrid.io/tutorials/deployments/deploy-aws/route-failover/This tutorial covers AWS route failover for a clustered Trustgrid deployment. On failover, the active member updates AWS route-table entries (ec2:CreateRoute / ec2:DeleteRoute) so that overlay CIDRs always point at the active member’s data ENI — no floating IP required. For the IP-based failover alternative, see AWS Cluster IP Failover. How it works Graceful Failover The Trustgrid appliance relinquishing the active role removes its AWS route-table entries. The appliance gaining the active role creates new route-table entries pointing at its own ENI.https://docs.trustgrid.io/tutorials/deployments/deploy-aws/l4-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://docs.trustgrid.io/tutorials/deployments/deploy-aws/l4-cluster/In an HA cluster, the cluster IP gives you a stable address that survives member failover. L4 connectors and services can both leverage it, depending on which side of the traffic flow the cluster sits on. Use one or both — they are independent. Connectors give clients a stable destination IP:port to connect to. Services give backends a stable source IP for connections originated from the cluster. Prerequisites A two-member Trustgrid HA cluster deployed in AWS.