Skip to main content
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog

Loading…

Servers Are Up

Your apps, automation and data on hardware we own. Build a private stack with predictable capacity and access through your dashboard, API or SSH.

SLA with service creditsOwned hardwareUS-based

Make room for your next idea

Explore the capacity, apps and access options that fit your workload. Check current availability and your total before you buy.

Sign up freeView Pricing

Products

  • Linux VPS
  • Windows VPS
  • Cloud & SaaS Services
  • Cloud Storage (Azure)
  • Virtual Datacenter
  • AI & Agent Hosting
  • Containers
  • Instant Apps
  • Software Platforms
  • Network builder
  • Game Servers
  • Pricing

Resources

  • Free Network Tools
  • 2026 Pricing Benchmark
  • Live SVG Badges
  • Latency & Speed Test
  • Guides & Tutorials
  • Documentation
  • API Reference
  • MCP Server
  • CLI & SDKs
  • OpenAPI & llms.txt
  • Use Cases
  • Free Migration
  • Uptime & Reliability
  • Datacenter
  • System Status
  • Network
  • Provider Comparisons Hub
  • Compare Providers

Company

  • About Us
  • Enterprise
  • Security Architecture
  • Trust Center
  • Blog
  • FAQ
  • Compliance
  • Startup Program
  • Open-Source Sponsorship
  • Press & Media Kit
  • Referral Program
  • Help Center
  • Contact Us
© Servers Are Up
TermsPrivacySLARefund PolicyDPAAcceptable Use
Service information
Docs
  • Documentation Hub
  • Choose a Product
    VMs, Containers & Cloud
  • First Linux Server
    SSH, Firewall & Apps
  • Windows Server 2025
    BYOL & Remote Desktop
  • Remote Access
  • Troubleshooting
  • FAQ
  • All Product Guides
    29 Step-by-Step Guides
  • Cloud & SaaS Catalog
    112 Cloud & SaaS Offerings
  • Azure Cloud Storage
    Hot/Cool/Archive & WORM
  • Resource Manager & RBAC
    Groups, Tags & Locks
  • Multi-Model Cloud DB
    JSONB, SQL & pgvector
  • Cloud Identity & ZTNA
    OIDC, SCIM & PIM
  • Key Vault & KMS
    Secrets & Envelope Keys
  • Cloud SIEM, SOAR & DLP
    Posture & Threat Response
  • API Gateway & Cloud DNS
    Edge WAF & DNS Zones
  • Serverless, Workflows & IoT
    Functions, Queues & DAGs
  • SaaS, Governance & Vault
    Budgets & Off-Host GRS
  • Build Web Apps with AI
  • Next.js and React
  • TypeScript and Node.js
  • npm and Tooling
  • Data and APIs
  • Deploy and Operate
  • Tutorials
  • Infrastructure
  • Automation & Regions
  • API Overview
  • API v1 Reference
    Endpoints & 23 Scopes
  • MCP Server
    129 AI Agent Tools
  • Swagger / OpenAPI 3.1
  • API Playground
  • Versioning & Sunset
  • API Token Security
    Authentication & Tokens
  • Instances API
    Compute Resources
  • Networking API
    Networks & Ports
  • Storage API Availability
    Volumes & Backups
  • Webhooks & Events
    Event Notifications
  • Rate Limits & Best Practices
    Throttling & Retries
  • sau CLI Reference
    34 Commands (v0.2)
  • Browser Web CLI
  • SDKs
  • Infrastructure as Code
    Terraform & Ansible
  • Code Examples
  • CLI & SDK Guides
  • Security Guides
  • Security at a Glance
  • Zero Trust Architecture
  • Live Trust Center
  • Compliance
Need help?

Loading documentation...

Documentation/products

Route APIs with Edge WAF, rate limits and Cloud DNS

Protect HTTP APIs behind managed L7 routes, subscription keys, rate limits, custom WAF rules and authoritative Cloud DNS zones.

Intermediate
18 min
Updated 2026-11-12

Deploy Ready-to-Run Infrastructure in Seconds

Linux VMs from $6/mo · Pooled Virtual Datacenters from $12/mo · Use code WELCOME20 for 20% off your first order.

Browse ServersView Pricing

Commands checked on 2026-11-12 with SAU API Gateway & Edge WAF v1.7, Cloud DNS, sau CLI 0.2.0.

What you will have at the end

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).

Before you start

  • One or more backend HTTP services running on Servers Are Up (such as a Linux VPS, Managed Docker stack, K3s Ingress, or Serverless Function).
  • A Personal Access Token with cloud:read and cloud:write scopes (Account settings > API keys at /account/api-keys).
  • Note on metering: 1,000,000 API Gateway & Edge WAF requests per month are included free on every account ($1.50 per 1M requests thereafter).

Steps

1. Create public (DNSSEC) and private (PRIVATE_VNET) Cloud DNS zones

Open 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.

2. Register an L7 API Gateway route with rate limits and subscription keys

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.

3. Configure Edge WAF rules and multi-origin failover pools

On the Edge WAF & Origin Pools tabs of Network > API gateway & edge WAF (/dashboard/api-gateway):

  1. Enable managed OWASP Core Rule Set protections (blocking SQL injection, XSS, command injection, path traversal, and known exploit scanners) in PREVENTION mode.
  2. Add custom geo, IP CIDR, header, or body-size WAF rules (for example blocking POST bodies larger than 1 MiB on /v1/auth/* or restricting /v1/admin/* to corporate VPN egress CIDRs).
  3. Define a primary + standby Origin Pool with active HTTP /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

4. Lock down your backend origin so callers cannot bypass the Gateway

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.

Check that it works

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.

What can go wrong

  • Legitimate webhook payloads with HTML/Markdown bodies trigger a 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.
  • Upstream origin URL rejected with 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).
  • DNSSEC validation fails (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).

Good practice

  • Version every public gateway path prefix explicitly (/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.
  • Set tighter per-minute rate limits (10–30 req/min) on login, password-reset, and AI inference routes than on cached GET endpoints (300–1200 req/min).
  • Run controlled DNS failover and latency drills in /dashboard/iot-chaos (sau iot chaos-run ...) before peak traffic events.

Where to go next

  • Put your own domain on an application and enable HTTPS
  • Open only the ports your application needs
  • Run serverless functions, workflows, queues and OCI registries

Related Articles

Create a scoped API key and send your first v1 request

Read more

Purchase Azure-backed cloud storage with WORM locks and SAS

Read more

Snapshot a server before a change and restore safely

Read more

Frequently Asked Questions

What does the Route APIs with Edge WAF, rate limits and Cloud DNS documentation guide cover?
Protect HTTP APIs behind managed L7 routes, subscription keys, rate limits, custom WAF rules and authoritative Cloud DNS zones. It is rated intermediate difficulty (18 min) and applies to Servers Are Up infrastructure and workflows.
Can I manage or automate these steps through the Servers Are Up dashboard, REST API v1, or MCP server?
Yes. Every Servers Are Up server includes browser-based SSH, WebRDP, and VNC console access in the dashboard, plus programmatic control via the REST API v1 (/api/v1) and hosted Model Context Protocol server (/api/mcp/v1) using a scoped Personal Access Token.

Need hands-on help with Route APIs with Edge WAF, rate limits and Cloud DNS?

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.

Was this article helpful?

On this page

What you will have at the endBefore you startSteps1. Create public (DNSSEC) and private (PRIVATE_VNET) Cloud DNS zones2. Register an L7 API Gateway route with rate limits and subscription keys3. Configure Edge WAF rules and multi-origin failover pools4. Lock down your backend origin so callers cannot bypass the GatewayCheck that it worksWhat can go wrongGood practiceWhere to go next