Guides
Task-focused walkthroughs for common Apoxy workflows.
The guides cover the patterns most teams hit operating Apoxy: opening tunnels into private networks, attaching routes and custom domains, redirecting and compressing traffic at the edge, and operating the in-cluster controller. Pick the one you need; each guide stands alone.
Tunnels
A · TUNNELSBasic tunnelsExpose a local HTTP server on your Apoxy domain using a tunnel.→B · DOCKERTunnels with DockerConnect a running Docker container to the Apoxy edge using a tunnel.→C · PRIVATE VPCPrivate services with VPC tunnelsPublish a private service through the default Gateway or call it from an Apoxy compute Service.→D · GCEGCE userspace VPC tunnelsDeploy an unprivileged VPC tunnel agent on a Compute Engine VM.→E · EC2EC2 kernel-mode VPC tunnelsDeploy a privileged VPC tunnel agent on EC2 with CloudFormation.→F · TUNINGTuning tunnelsAdjust endpoint selection, connection pooling, and DNS behavior for tunnel clients.→G · K8SRouting to Kubernetes servicesAddress cluster services through a tunnel and the Apoxy edge.→
Routing and TLS
H · ROUTINGRouting trafficAttach routes to the default Gateway and verify traffic flow using the Gateway API.→I · DOMAINSCustom domainsAttach a customer-owned domain to Apoxy's default Gateway with zero-downtime TLS provisioning.→J · REDIRECTHTTP to HTTPS redirectRedirect HTTP traffic to HTTPS using the default Gateway's listeners.→K · COMPRESSIONResponse compressionCompress HTTP responses with gzip, brotli, or zstd - enabled by default, customizable via HTTPRouteFilter.→
Operations
L · ROTATIONRotating the kube-controller certificateRoll the per-cluster client certificate the Apoxy controller uses, without dropping the aggregated API.→M · MCPQuery logs with Claude CodeConnect Claude Code to Apoxy's MCP server to query your proxy logs with natural language.→N · DEBUGTroubleshootingDebug route attachments, tunnel connectivity, and common failure modes.→