Вход на сайт

Просмотр новости

Найдите то, что Вас интересует

Announcing temporal policies and rate limiting in Amazon Bedrock AgentCore

Дата публикации: 06-08-2026 04:00:00

Amazon Bedrock AgentCore announces two new controls: temporal policies for stateful agent authorization and rate limiting for AI traffic.
Temporal policies let you define stateful authorization rules that evaluate each request in the context of an agent's prior actions within a session, because a single tool call can be safe in isolation yet harmful given what preceded it. With temporal policies you can enforce workflow sequencing, require that a tool argument exactly matches the output of a prior call, require human approval before taking privileged actions, and enforce data freshness.
Rate limiting enables per-user or per-group controls over how much traffic flows to the tools, models, and agents connected to your gateway. Using rules scoped by OAuth or AWS IAM, you can set rate limits on requests across all target types, tokens for inference targets, and concurrent connections to cap long-lived concurrent sessions, aiding downstream service availability and enforcing fair limit distribution. 
For regional availability and to learn more, see the documentation, read the announcement blog, and explore the Dogwood reference implementation. 

Основное содержимое страницы с новостью.

Amazon Bedrock AgentCore announces two new controls: temporal policies for stateful agent authorization and rate limiting for AI traffic.

Temporal policies let you define stateful authorization rules that evaluate each request in the context of an agent's prior actions within a session, because a single tool call can be safe in isolation yet harmful given what preceded it. With temporal policies you can enforce workflow sequencing, require that a tool argument exactly matches the output of a prior call, require human approval before taking privileged actions, and enforce data freshness.

Rate limiting enables per-user or per-group controls over how much traffic flows to the tools, models, and agents connected to your gateway. Using rules scoped by OAuth or AWS IAM, you can set rate limits on requests across all target types, tokens for inference targets, and concurrent connections to cap long-lived concurrent sessions, aiding downstream service availability and enforcing fair limit distribution. 

For regional availability and to learn more, see the documentation, read the announcement blog, and explore the Dogwood reference implementation

Схожие новости

#Наименование новостиТональностьИнформативностьДата публикации
1Amazon Bedrock AgentCore adds memory, policy, and harness in AWS GovCloud (US-West)08.2107-08-2026
2AgentCore payments is now generally available in Amazon Bedrock AgentCore05.4518-08-2026
3AgentCore runtime instances are now generally available09.506-08-2026
4Amazon Bedrock expands IAM principal cost allocation to the bedrock-mantle endpoint08.7811-08-2026
5Your AI agent’s next tool call may be valid but wrong. AWS’s Dogwood promises to fix that.016.0806-08-2026
6Amazon Quick now supports per-user resource limits09.514-08-2026
7Amazon Bedrock now supports SpaceXAI Grok 4.609.7819-08-2026
8How AWS Bedrock is shaping Model Context Protocol012.1422-04-2026
9AI Agent Governance: Securing Autonomous Agents in Production010.4124-07-2026

Классификация: Пресс-релизы. Схожих патентов: 0. Схожих новостей: 9. Тональность: 0. Информативность: 4.9. Источник: aws.amazon.com.