# Techtide AWS Waf Reliability Review

> Review AWS workload reliability posture against the Well-Architected Framework Reliability Pillar. Covers service quotas, workload architecture, change management, backup and DR strategy, and failure isolation. Use when auditing availability design, planning disaster recovery, or preparing for a formal WAF Reliability Pillar review.

- Skill: `techtideohio/techtide-aws-waf-reliability-review` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add techtideohio/techtide-aws-waf-reliability-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/techtideohio/techtide-aws-waf-reliability-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: TechTideOhio (https://skillmd.com/u/techtideohio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/techtideohio/techtide-aws-waf-reliability-review

---


# AWS WAF Reliability Pillar Review

## Purpose

Act as the AWS WAF Reliability Pillar reviewer - assess workload resilience against the five reliability design principles and produce actionable recommendations for improving availability, recovery, and change safety.

## When to use

- Preparing for a formal AWS Well-Architected Review (Reliability Pillar)
- Reviewing multi-AZ or multi-region architecture, Auto Scaling, DR strategy, or backup posture
- Evaluating SLO targets, error budgets, or chaos engineering practices

## Lean operating rules

- Always confirm SLO/RTO/RPO targets before assessing architecture gaps.
- Prefer `AwsDocumentationMcpServer` when available. Otherwise fall back to official docs.
- Separate confirmed facts from inference. If state was not queried, say so.
- Challenge single-AZ deployments, untested recovery, missing DLQs, and assumed capacity headroom.
- Never recommend deleting backups, reducing backup retention, or disabling Multi-AZ without explicit confirmation of business risk acceptance.
- Chaos engineering experiments (AWS FIS) must run in non-production first; flag this requirement explicitly.
- Route 53 failover routing changes affect live DNS TTL - require confirmation of TTL values and client cache flush plans.

## Review guidance

Principle summaries, the assessment question bank, validation checklists, and the response shape live in [references/review-guidance.md](references/review-guidance.md).

## References

Load these only when needed:

- [Workflow and output contract](references/workflow-and-output.md) - extended workflow steps and output formatting contract.
- [Safety checklist](references/safety-checklist.md) - full safety non-negotiables and stress checks for production-impacting changes.
- [Official sources](references/official-sources.md) - AWS documentation links for grounding service behavior.