Production CDN, DNS, cache, and rollback plan.

Use this runbook to validate docs-dev, docs-tst, and production docs cutover, capture DNS and CDN evidence, invalidate cache, verify response headers, assign owners, and decide whether to go, hold, or roll back.

Cutover Snapshot

Launch hosts: 3
Default TTL: 3600s
Max TTL: 86400s
Rollback mode: Redeploy or S3 versions

Environment Promotion Order

Docs cutover validation by environment
Environment	Hostname	Account prefix	Required validation	Owner
Development	docs-dev.stornamics.com	202-ue2-dev	Pipeline success, DNS alias check, HTTPS header check, sitemap and LLM route check, and Playwright smoke from an approved network.	docs platform reviewer
Test	docs-tst.stornamics.com	203-ue2-tst	Same checks as development, plus release-owner confirmation that the candidate artifact matches the intended commit.	release owner
Production	docs.stornamics.com	207-ue2-prd	Same checks as test, plus cache invalidation ID, post-invalidation header sample, route smoke evidence, support watch owner, and go/no-go record.	release owner

Cutover Gates

Required evidence before promotion and launch watch
Gate	Required evidence	Go/no-go rule
Source candidate	Commit SHA, branch or PR, npm run build, docs validators, and required Playwright result against localhost or an approved docs target.	No P0 or P1 source, build, route, privacy, support, or browser defect remains unassigned.
Deploy development	Development pipeline run ID, deploy outcome, HTTPS headers, DNS evidence, and route-smoke target.	Do not promote if the host redirects unexpectedly, returns a failed status, omits route manifests, or hides the deployed commit.
Deploy test	Test pipeline run ID, deployment artifact identity, route-smoke result, and support/privacy/legal route checks.	Do not promote if test differs from development without an accepted release-owner note.
Pre-production review	Distribution ID, expected alias record, cache policy name, planned invalidation paths, rollback mode, and launch watch owner.	Do not cut over until every evidence field has an owner and the rollback mode is executable by that owner.
Deploy production	Production pipeline run ID, DNS alias result, HTTPS headers, route manifests, core route smoke, cache invalidation ID, and support watch start time.	Go only when release owner, docs platform, docs QA, and support owners accept the evidence record.
Launch watch	Same-day check of home, search, status, support, legal, feedback, operations, product hubs, no-result search signal, and 404 behavior.	Roll back or hold launch state when a P0 or P1 condition from DOCS-090 or DOCS-093 appears.

DNS And CDN Checks

DNS, TLS, route rewrite, manifest, and distribution checks
Check	Command or console evidence	Expected record	Owner
Route 53 alias	dig +short docs-dev.stornamics.com, docs-tst.stornamics.com, and docs.stornamics.com from a release workstation.	Each hostname resolves through the expected CloudFront alias chain or the reviewer records the observed DNS path.	docs platform reviewer
TLS and redirect	curl -I https://<hostname>/ for each environment.	HTTPS is reachable, production stays on the docs host, and any non-production access gating is recorded.	docs QA reviewer
Route rewrite	curl -I https://<hostname>/operations/production-cdn-rollback/ and one product route without index.html.	Extensionless routes resolve through the CloudFront function and return a docs response below HTTP 400.	docs platform reviewer
Route manifests	curl -I https://<hostname>/sitemap.xml, curl -I https://<hostname>/llms.txt, and browser check for /search/.	Generated assets are present for the deployed route inventory.	docs QA reviewer
Distribution identity	CloudFront console, Terraform state, or deployment output for the target environment.	Evidence names the distribution ID, alias hostname, cache policy name, and function name.	release owner

Cache And Invalidation Checks

Cache headers, invalidation, and post-invalidation evidence
Surface	Evidence to capture	Expected disposition
HTML routes	Header samples for home, one roadmap route, one operations route, and one product route.	Record cache-control, etag, age, x-cache, and status. If object headers are absent or surprising, docs platform decides whether launch needs a response-header policy change.
Static assets	One fingerprinted JavaScript or CSS asset from the built page.	Record cache-control, etag, age, and x-cache; long-lived fingerprinted assets are acceptable only when HTML can be invalidated and route manifests stay current.
Invalidation	CloudFront invalidation request for /* or the release-owner approved path set.	Record distribution ID, invalidation ID, requester, start time, completion time, and paths.
Post-invalidation sample	Repeat the HTML, sitemap, LLM, and core-route header checks after invalidation completes.	The response reflects the intended build or accepted rollback target before launch watch begins.

Rollback Procedure

Rollback actions and evidence owners
Phase	Action	Owner	Evidence
Stop promotion	If development or test validation fails, stop the next environment promotion and attach the failed command, hostname, and pipeline run ID.	release owner	Failed validation row and owner decision.
Prefer redeploy	Redeploy the last accepted commit or artifact through the approved pipeline when the previous artifact identity is known.	docs platform reviewer	Previous commit SHA, pipeline run ID, deploy result, and post-deploy smoke evidence.
Restore S3 versions	When pipeline redeploy is unavailable, restore previous object versions for both primary and secondary docs buckets using bucket versioning evidence.	operations reviewer	Bucket names, object version IDs, restore command transcript, and reviewer approval.
Invalidate cache	Invalidate /* or the approved affected path set after redeploy or object-version restore.	docs platform reviewer	CloudFront distribution ID, invalidation ID, path set, completion time, and post-invalidation headers.
Revalidate	Run route, DNS, header, sitemap, LLM, support/legal, feedback, and Playwright smoke checks against the rollback target.	docs QA reviewer	Passed commands, target hostname, timestamp, and residual risks.
Notify watch owners	Update post-launch triage, support owner, release owner, and final launch acceptance notes with the rollback reason and current public state.	release owner	Dated status note and owner signoff.

Owner Decision Record

Required owner decisions for go, hold, or rollback
Owner	Owns	Required decision
Release owner	Promotion order, hold or rollback decision, final go/no-go evidence, and launch watch handoff.	Accept, hold, or roll back after reviewing the environment evidence table.
Docs platform reviewer	Terraform source mapping, deployment output, CloudFront distribution, DNS alias, invalidation, and cache-header evidence.	Confirm the deployed host matches the intended infrastructure and cache behavior.
Operations reviewer	S3 bucket versioning, object restore path, response, and rollback execution.	Confirm rollback steps are executable and evidence-safe.
Docs QA reviewer	Gatsby route behavior, route manifests, local or remote Playwright result, and browser smoke evidence.	Confirm the docs site passes source and browser validation on an approved docs target.
Support reviewer	Customer-safe status, feedback, support route, launch watch intake, and escalation handoff.	Confirm readers have a support path during cutover and rollback.
Security reviewer	Access gating, DNS/TLS evidence, credential handling, and rollback transcripts.	Confirm evidence does not expose credentials, private account details beyond approved environment IDs, or customer data.

Go/No-Go Evidence

Evidence fields required before DOCS-104 final acceptance
Evidence field	Required value
Build identity	Commit SHA, PR or merge record, pipeline run ID, and deployed artifact identity when available.
Environments checked	docs-dev.stornamics.com, docs-tst.stornamics.com, and docs.stornamics.com with timestamps.
Validation commands	npm run build, docs validators, route manifest validation, and required Playwright command with DOCS_SITE_BASE_URL.
DNS and TLS	DNS alias result, HTTPS header sample, certificate status or console evidence, and redirect outcome.
CDN and cache	Distribution ID, function name, cache policy name, cache-header samples, invalidation ID, and post-invalidation sample.
Rollback readiness	Previous accepted commit or artifact, rollback mode, owner, command evidence, and stop condition.
Open risks	Any P0/P1/P2 item with owner, due date, deciding reviewer, and accepted launch posture.
Decision	go, hold, or rollback, signed by release owner, docs platform reviewer, docs QA reviewer, and support reviewer.

Limits And Follow-Ups

Dependency Audit

Use DOCS-102 for npm, Gatsby, .NET automation, Playwright, license, vulnerability, private-feed, and remediation decisions.

Observability Hooks

Use DOCS-103 for deployment health, 404s, failed searches, client-side errors, page-load regressions, feedback signals, and incident hooks.

Final Acceptance

Use DOCS-104 for the exact build, validation commands, reviewer signoffs, unresolved risks, launch watch plan, and final decision.

Launch QA
Available: DOCS-090
Use the blocker rules, validation gates, browser expectations, and accepted risk model during cutover.
Post-launch triage
Available: DOCS-091
Use the launch-watch owner cadence and severity routing after production promotion.
Support bundle and privacy
Available: DOCS-056
Apply redaction and privacy review rules before publishing deployment or rollback evidence.
Operations index
Available
Return to the global operations route for runbook, troubleshooting, observability, and support paths.