Question

A financial services company runs a customer-facing chatbot on Amazon Bedrock using Anthropic Claude. During market-open hours the traffic spikes predictably to about 12x baseline for roughly 90 minutes, and users experience throttling errors (ThrottlingException) because the on-demand account-level quota is exceeded. Outside these windows, traffic is low and steady. The team wants to eliminate throttling during the spike while minimizing cost the rest of the day. What is the most appropriate approach?

Accepted Answer

Purchase Provisioned Throughput with a no-commitment (hourly) term, activate the model units before the market-open window, and release them after the spike subsides while serving off-peak traffic on-demand.

Answer

Purchase Provisioned Throughput with a monthly commitment term sized to the peak spike, and route all traffic through it at all times.

Answer

Implement client-side exponential backoff with jitter and rely solely on on-demand throughput, accepting retries during the spike.

Answer

Switch to a smaller model during the market-open window to fit within the existing on-demand quota, then switch back afterward.