Domains and App Shield

stackblaze domain

Alias: domains

Manages custom domains for the linked app. list (alias ls) shows each domain with its verification and certificate status; add prints the DNS records to create; verify checks DNS now; remove (alias rm) detaches a domain; status shows the app's hosts, whether each has TLS, and the project's wildcard domain.

stackblaze domain [list]
stackblaze domain add <host> [--wait] [--timeout <seconds>] [--takeover]
stackblaze domain verify <host> [--wait] [--timeout <seconds>]
stackblaze domain remove <host> [-y]
stackblaze domain status [host]

domain add prints two records: a TXT record at _stackblaze-verify.<host> that proves you own the domain, and a CNAME from <host> to the app's platform URL. Once DNS verifies, the HTTPS certificate is issued automatically. A domain moves from waiting for DNS, to DNS verified, to issuing certificate, to active.

The platform re-checks pending domains every 5 minutes. verify checks right away, and --wait keeps checking until the domain is active; it exits 1 with the reason when the domain ends in an error or the timeout passes.

Several accounts can claim a domain that is not verified yet: the first claim whose TXT record verifies gets it, and the others are released. If another account verified a domain but no longer controls its DNS, add --takeover claims it; it moves to you once your TXT record is live and theirs has been gone for checks at least 10 minutes apart, so pass --wait --timeout 1800 or more.

Also accepts the scope flags (-p, --pipeline, --phase, -a, --app) and the output flags (-o, --output, --json), plus --token and --api-url. Common flags

Examples

stackblaze domain add www.example.com          # prints the DNS records to create
stackblaze domain verify www.example.com --wait
stackblaze domain add www.example.com --wait --timeout 900
stackblaze domain list
stackblaze domain remove old.example.com -y

stackblaze waf

App Shield is the per-app web application firewall. enable turns it on in detection-only mode (blocking stays on if it already was); disable turns it off. under-attack enable switches to blocking mode, and under-attack disable returns to detection-only.

stackblaze waf [status]
stackblaze waf enable
stackblaze waf disable
stackblaze waf under-attack status|enable|disable

Also accepts the scope flags (-p, --pipeline, --phase, -a, --app) and the output flags (-o, --output, --json), plus --token and --api-url. Common flags

Examples

stackblaze waf enable
stackblaze waf under-attack enable
stackblaze waf status -o json