Trigger and scope

CRITICAL: many subcommands have unintuitive paths (e.g. fastly domain create fails with 403, correct is fastly service domain create; logging is under fastly service logging; alerts under fastly service alert; rate limits under fastly service rate-limit).

Covers: services, backends, domains, VCL snippets, cache purging, Compute/WASM deploys, log streaming (S3/Datadog/Splunk/Kafka/25+ providers), NGWAF/WAF, TLS/mTLS, KV/config/secret stores, stats, alerts, rate limiting, ACLs, and auth tokens.

Fastly CLI Overview

Prerequisites

Requires the fastly CLI; API operations also need network access to Fastly. For installation, see https://www.fastly.com/documentation/reference/cli/. JSON examples also need jq; origin checks use curl and openssl. Compute builds need the project's language toolchain and dependencies.

Use credentials already configured in the user's local CLI or environment. If authentication is missing, have the user complete fastly auth login --sso locally or configure FASTLY_API_TOKEN outside chat. Never ask for an API key in chat, print a token, or enable shell tracing on authenticated commands.