AmneziaWG upstreams
Use type: amneziawg with the same provider-file shape as WireGuard. The [Interface] section may additionally contain Jc, Jmin, Jmax, S1, S2, H1, H2, H3, and H4. Names are canonicalized case-insensitively and passed to awg set.
[Interface]PrivateKey = SYNTHETIC-PRIVATE-KEY-REPLACE-BEFORE-USEAddress = 192.0.2.2/32Jc = 4Jmin = 64Jmax = 256S1 = 0S2 = 0H1 = 1H2 = 2H3 = 3H4 = 4
[Peer]PublicKey = W/kKaUP1n48AgIzxs8po0HKV+UEk1vMcTuBW648atSE=Endpoint = awg.example.com:51820AllowedIPs = 0.0.0.0/0Provider parameters must match the provider; they are not interchangeable performance knobs. Encrypt the real file because it contains PrivateKey. The upstream parameters affect only that provider namespace. hub.awg_interface separately controls the client-facing ingress and is copied into device profiles.
Validate the YAML and run a configured probe after deployment. The synthetic file above is intentionally unusable.
Next: Hub ingress parameters and Tunnel fields.