Loading…
Loading documentation...
Protect HTTP APIs behind managed L7 routes, subscription keys, rate limits, custom WAF rules and authoritative Cloud DNS zones.
Commands checked on 2026-11-12 with SAU API Gateway & Edge WAF v1.7, Cloud DNS, sau CLI 0.2.0.
Your public and partner HTTP APIs will sit behind Network > API gateway & edge WAF (/dashboard/api-gateway) with path-based layer-7 routing, subscription key enforcement, per-minute token-bucket rate limits, custom OWASP SQLi/XSS/bot WAF rules, and multi-origin health failover—paired with authoritative public (DNSSEC) and split-horizon private (PRIVATE_VNET) zones in Network > Cloud DNS zones (/dashboard/cloud-dns).
cloud:read and cloud:write scopes (Account settings > API keys at /account/api-keys).$1.50 per 1M requests thereafter).DNSSEC) and private (PRIVATE_VNET) Cloud DNS zonesOpen Network > Cloud DNS zones (/dashboard/cloud-dns) or use sau network dns-create to separate external internet resolution from internal VPC service discovery:
# Public authoritative zone with DNSSEC signing enabled
sau network dns-create example-api.com --dnssec
# Split-horizon private zone visible only inside your private VPC fabric
sau network dns-create internal.example-api.com --private
sau network dns-list -o table
Add A, AAAA, CNAME, TXT, MX, or CAA records in /dashboard/cloud-dns (or POST /api/v1/cloud-dns) and export a standard RFC 1035 BIND zone file whenever you want an offline backup in Git.
Open Network > API gateway & edge WAF (/dashboard/api-gateway) or call POST /api/v1/apim to publish a versioned gateway route in front of your backend origin:
curl -fsSL -X POST "https://serversareup.com/api/v1/apim" \
-H "Authorization: Bearer sau_your_token_here" \
-H "Content-Type: application/json" \
-d '{
"action": "create-route",
"name": "orders-v1-public",
"pathPrefix": "/v1/orders",
"upstreamUrl": "https://origin-orders.example-api.com",
"methods": ["GET", "POST"],
"rateLimitPerMinute": 300,
"requireSubscriptionKey": true,
"wafMode": "PREVENTION"
}' | jq .
Generate partner or mobile-app Subscription Keys on /dashboard/api-gateway so each external consumer authenticates at the edge (Ocp-Apim-Subscription-Key / X-SAU-Subscription-Key) with independent rate quotas before traffic ever touches your origin CPU or database connections.
On the Edge WAF & Origin Pools tabs of Network > API gateway & edge WAF (/dashboard/api-gateway):
PREVENTION mode.POST bodies larger than 1 MiB on /v1/auth/* or restricting /v1/admin/* to corporate VPN egress CIDRs)./healthz probes so traffic shifts automatically to your secondary server or region if the primary origin returns 5xx or times out.# Inspect all active API Gateway routes, subscription keys, and WAF origin pools
sau network apim-list
An API Gateway or WAF only protects an origin if attackers cannot connect directly to the origin's raw IPv4 address! On Network > Firewall (/dashboard/network?tab=firewall) (or via mutually authenticated upstream headers / private VPC routing), restrict your origin server's inbound port 443 so only traffic routed through your gateway or private mesh is accepted.
Verify your DNS records, gateway route health, rate-limit enforcement, and WAF SQL-injection block behavior:
# 1. Confirm gateway routes and WAF mode
sau network apim-list -o json | jq '.routes[] | {name, pathPrefix, rateLimitPerMinute, wafMode}'
# 2. Test a simulated SQL injection query parameter against a WAF-protected route (expects 403)
curl -s -o /dev/null -w "%{http_code}\n" "https://gateway.example-api.com/v1/orders?id=1%27%20OR%201%3D1--"
Check Operations > Cloud SIEM & SOAR (/dashboard/sentinel) to see blocked WAF events logged with rule IDs and client fingerprints.
403 XSS WAF rule. Scope rich-content upload or CMS endpoints to targeted rule exclusions (while keeping SQLi and SSRF rules active) rather than switching the entire gateway from PREVENTION to DETECTION.400 Bad Request. Public gateway upstreamUrl entries validate against SSRF targets (127.0.0.1, link-local 169.254.169.254, and internal control-plane addresses are refused).SERVFAIL on 1.1.1.1) after moving registrars. Remove stale DS records at your domain registrar before changing authoritative nameservers, wait for the old DS TTL to expire, and then publish the new DS digest from Network > Cloud DNS zones (/dashboard/cloud-dns)./v1/orders, /v2/orders) and catalog all schemas in Automation > IoT, Digital Twins & resilience (/dashboard/iot-chaos API Center tab) so consumers have a clear deprecation window.10–30 req/min) on login, password-reset, and AI inference routes than on cached GET endpoints (300–1200 req/min)./dashboard/iot-chaos (sau iot chaos-run ...) before peak traffic events.Every Servers Are Up virtual machine and container includes an integrated HTML5 browser-based SSH, RDP, and VNC console in your dashboard, default-off inbound firewall rules with per-IP allow-lists, and full programmatic control via REST API v1 and Model Context Protocol (MCP). Explore our Virtual Datacenter Plans or reach out to Servers Are Up Support.