Establish the base
CUR line items identify what was paid for the affected service and scope.
AWS SLA credit recovery
Find AWS service credits before the claim window closes.
Upload your cost, AWS Health, and downtime evidence. AllCaps matches affected services and regions to the applicable SLA tier, quantifies supported credits, and tracks the filing deadline.
Run a free finding No signup for the aggregate preview
Claim-only credits
Three-way evidence match
Charge base
Service, region, resource, and month
Incident scope
AWS Health event and affected resources
Downtime proof
Customer metrics or request logs
Prove the outage
AWS Health corroborates the event; CloudWatch or request logs establish SLA-defined unavailability.
Protect the window
Covered SLAs require a Support Center claim by the end of the second billing cycle after the incident.
Evidence standard
An SLA recovery audit, not cloud cost optimization.
An incident notice alone does not prove SLA eligibility. Each service defines availability differently—request error rates, failed connection intervals, external connectivity, or concurrent multi-AZ failure. The audit keeps incomplete cases visible without presenting them as money owed.
Amazon EC2
Region-level and single-instance commitments, with non-stacking rules.
Amazon S3
Storage-class commitments and 5-minute qualifying error rates.
AWS Lambda
Regional 5-minute availability from qualifying 500/503 errors.
Amazon RDS
Multi-AZ and Single-DB commitments based on failed connection intervals.
Read and quantify only. No AWS changes and no claim filing.AWS Service Level Agreements