AWS Bedrock SLA Credits & Refunds

Bedrock outages cost engineering teams twice: once in lost productivity, and again in unclaimed service credits sitting on the table because nobody filed a ticket in time. Here's how the Bedrock SLA actually works, what AWS will and won't credit you for, and how teams are automating the claim process end-to-end.

What this guide covers

• The official AWS Bedrock uptime commitment and credit tiers
• Which incidents qualify (and which exclusions silently disqualify claims)
• How to file a Bedrock credit request inside the AWS claim window
• Why manual claim recovery typically leaves money on the table

Frequently asked questions about AWS Bedrock SLAs

What is the typical SLA uptime guarantee for AWS Bedrock?

The Amazon Bedrock SLA targets a 99.9% Monthly Uptime Percentage, with tiered service credits beginning when uptime drops into the 99.0-99.9% range (10% credit), 95.0-99.0% (25%), or below 95.0% (100%). Note that Bedrock's SLA covers the on-demand inference endpoints; throughput reserved via Provisioned Throughput may have separate terms.

How do I claim AWS Bedrock SLA credits after an outage?

Open a billing case in the AWS Support Center within 60 days of the affected billing period (the exact window is in the Bedrock SLA itself). The case needs: the affected resource IDs, timestamps of the disruption in UTC, your monitoring evidence (CloudWatch metrics, error logs, or third-party uptime monitoring) cross-referenced against the AWS Health Dashboard, and your calculation of the Monthly Uptime Percentage. AWS reviews the case manually and applies any granted credit to your next invoice rather than refunding cash. Teams that file these regularly automate the evidence-gathering step because it's the most error-prone — a claim missing the wrong field gets denied and has to be refiled.

What exclusions apply to the AWS Bedrock SLA?

Bedrock-specific exclusions also cover model-level throttling caused by exceeding your account's request quota and errors returned because a requested foundation model was not enabled in your region — these are customer-side issues, not Bedrock unavailability.

Why is it difficult to get refunds for Bedrock outages manually?

AI/ML SLAs are still maturing, and Bedrock carries some of the most nuanced terms in the cloud catalog. Rate limits, queue depths, and model availability all get measured differently, and the SLA often excludes throttling that the provider deems "expected." Teams that successfully claim Bedrock credits do so by capturing per-request latency and error-code data and matching it precisely against the published terms.

Related AWS SLA guides

Other AWS services that share the same claim window and Support Center workflow:

• AWS SageMaker SLA credits — AI/ML
• AWS EC2 SLA credits — Compute
• AWS S3 SLA credits — Storage
• AWS RDS SLA credits — Database

Stop leaving AWS credits unclaimed

The hardest part of recovering Bedrock credits isn't the SLA — it's the lag between an outage and the moment somebody on your team has the bandwidth to file the case. By the time the FinOps team gets around to it, the evidence has rolled out of CloudWatch and the billing window is closing.

Next Signal watches AWS Health and your own observability data, detects Bedrock SLA breaches in real time, assembles the evidence package the way AWS expects it, and files the billing case for you. See how it works or start a free trial.