Service Quotas

Review the service quotas below before deploying AVX. The defaults for new AWS accounts may require increases before reaching production-level load.

Quota reference

Service	Quota	Default limit	Increase path
Amazon Bedrock — model invocation	Requests per minute (RPM) and tokens per minute (TPM) per model per region	Varies by model and region; Claude Sonnet and Nova 2 Sonic both have default quotas that may be insufficient for multi-tenant production load	Request a quota increase in the Bedrock console under Service Quotas
Amazon Bedrock AgentCore Runtime	Concurrent runtime invocations; invocations per second per runtime	Default concurrent invocations are modest; multi-tenant concurrent voice sessions may require increases	AgentCore quotas; request increases via the Service Quotas console
Amazon Connect	Concurrent contacts per instance; contact flows per instance; queues per instance	New instances have conservative defaults; a multi-tenant production deployment with a chat queue and a callback queue per tenant may approach limits	Amazon Connect service quotas; request increases via Service Quotas or the Connect console
AWS Lambda	Concurrent executions per region	1,000 (default, adjustable)	Lambda quotas; request increases via Service Quotas
Amazon DynamoDB	Read/write capacity units (on-demand) or provisioned throughput	On-demand mode auto-scales; provisioned mode requires manual planning	DynamoDB quotas

Tip

Request Bedrock model quota increases before onboarding a real workload — increases for Claude Sonnet and Nova 2 Sonic in your target region can take several business days to process. Plan for a two-week lead time for quota requests on high-demand models.

Quota monitoring

AVX emits CloudWatch metrics for model invocation rates and AgentCore runtime invocations. Set CloudWatch alarms on these metrics at 80% of your quota thresholds to give advance warning before throttling affects customers. See the Security chapter for guidance on monitoring and audit logging.