Skip to content

Bedrock Agent InvokeAgent API throttling despite Service Quota increase

0

I'm experiencing persistent throttlingException errors with Amazon Bedrock Agent despite increasing the Service Quota.

Issue Details:

  • Error message: "An error occurred (throttlingException) when calling the InvokeAgent operation: Your request rate is too high. Reduce the frequency of requests"
  • Region: ap-northeast-1
  • Agent ID: CBVGRSYMD0
  • Alias ID: TSTALIASID

What I've tried:

  1. Increased "APIs per Agent" Service Quota from 11 to 50 (approved on Sept 22, 2025)
  2. Added sleep delays in Lambda function
  3. Using different session IDs for each request
  4. Searched for InvokeAgent rate limit quotas but couldn't find them in Service Quotas

Current Setup:

  • Lambda function calling bedrock-agent-runtime InvokeAgent API
  • API Gateway integrated with Lambda
  • Frontend on GitHub Pages
  • Single user testing (not high traffic)

Even with just 1-2 requests per minute, I'm getting throttling errors.

Is there a specific Service Quota for InvokeAgent API rate limits that I'm missing? Or is there another configuration needed to resolve this issue?

Any help would be greatly appreciated!

2 Answers
7

Would suggest:

  1. Enable Exponential Backoff with Jitter • AWS recommends implementing retries with exponential backoff and random jitter to avoid retry storms:
for attempt in range(retries):
    try:
        response = client.invoke_agent(...)
        return response
    except client.exceptions.ThrottlingException:
        wait_time = delay * (2 ** attempt) + random.uniform(0, 1)
        time.sleep(wait_time)
  1. Use Cross-Region Inference Profiles • Bedrock maintains independent capacity pools per region. • You can route requests across regions (e.g., ap-northeast-1, us-west-2) to avoid localized throttling.
  2. Contact AWS Support for Agent-Specific Limits • Some quotas (like InvokeAgent RPM) are not adjustable via Service Quotas UI. • Open a support case and request: o Specific InvokeAgent RPM and TPM limits for your agent. o Increase for those limits if needed.
  3. Check for Agent Configuration Bottlenecks • If your agent uses complex action groups, knowledge bases, or trace enablement, it may consume more tokens per request. • Try disabling enableTrace or simplifying the agent flow.
EXPERT

answered a year ago

AWS
EXPERT

reviewed a year ago

0

Hey,

Hope you're keeping well.

The InvokeAgent API has its own internal throttling limits that aren’t exposed in the Service Quotas console, so increasing the “APIs per Agent” quota won’t remove those caps. Bedrock recommends implementing retries with exponential backoff and jitter, as even low request rates can hit per‑second or burst limits depending on agent configuration. Also check CloudWatch metrics for ThrottlingException under the AWS/Bedrock namespace to confirm actual request patterns. If the throttling persists at very low rates, open an AWS Support case with the agent ID and timestamps so they can verify backend limits specific to your account and region.

Thanks and regards,
Taz

answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.