Skip to content

Troubleshooting Playbooks Hub

This hub groups Elastic Beanstalk remediation playbooks by failure pattern so responders can move from diagnosis to evidence-backed action without skipping verification.

How to Use Playbooks

  • Start from Decision Tree to classify the incident before picking a remediation path.
  • Run one of the First 10 Minutes checklists to preserve the first evidence.
  • Choose the playbook that best matches the dominant symptom and disprove competing hypotheses before changing configuration.
  • Execute one playbook at a time, then verify health, user impact, and rollback readiness before continuing.
flowchart TD
    A[Incident observed] --> B[First 10 Minutes checklist]
    B --> C[Decision Tree classification]
    C --> D{Dominant failure pattern}
    D --> E[Deployment and Availability]
    D --> F[Performance]
    D --> G[Networking]
    E --> H[Specific playbook]
    F --> H
    G --> H
    H --> I[Collect evidence]
    I --> J[Apply mitigation]
    J --> K[Verify health and user impact]

Playbook Standard

All 16 playbooks use the same responder-oriented structure:

  • 9 sections from Summary through Prevention.
  • 2 Mermaid diagrams: decision flow and evidence timeline.
  • EB CLI and AWS CLI investigation commands with sample output.
  • CloudWatch Logs Insights queries with example output tables.
  • Normal vs Abnormal comparison tables plus Common Misreadings.

Category Index

Deployment and Availability

Performance

Networking

See Also

Sources