adobe-incident-runbook

# Adobe Incident Runbook ## Overview Rapid incident response procedures for Adobe API-related outages, covering IMS authentication failures, Firefly/Photoshop API downtime, PDF Services quota exhaustion, and I/O Events delivery failures. ## Prerequisites - Access to Adobe Developer Console and Admin Console - Access to application monitoring (Grafana, Datadog, etc.) - kubectl access to production cluster (if applicable) - Communication channels (Slack, PagerDuty) ## Severity Matrix | Level | Definition | Response Time | Example | |-------|------------|---------------|---------| | P1 | Complete Adobe integration failure | < 15 min | IMS auth broken, all APIs down | | P2 | Single API degraded | < 1 hour | Firefly 429s, Photoshop timeouts | | P3 | Minor impact | < 4 hours | Webhook delays, slow PDF extraction | | P4 | No user impact | Next business day | Monitoring gap, metric anomaly | ## Quick Triage (Run These First) ```bash # 1. Is Adobe itself down? curl -s -o /dev/null -w "Adobe Status: %{http_code}\n" https://status.adobe.com # 2. Can we generate an access token? curl -s -o /dev/null -w "IMS Auth: %{http_code}\n" -X POST \ 'https://ims-na1.adobelogin.com/ims/token/v3' \ -d "client_id=${ADOBE_CLIENT_ID}&client_secret=${ADOBE_CLIENT_SECRET}&grant_type=client_credentials&scope=${ADOBE_SCOPES}" # 3. Can we reach each API endpoint? for endpoint in firefly-api.adobe.io image.adobe.io pdf-services.adobe.io; do CODE=$(curl -s -o /dev/null -w "%{http_code}" --conne...