All news with #bedrock agents tag

🔗 Amazon Quick now integrates with the AWS Agent Registry to let users discover, enable, and share MCP servers and agents directly within their Amazon Quick workspace. Connection details are pre-populated from the registry, enabling quick enablement and distribution for chat, agents, apps, flows, and research. The integration is available in all regions where Amazon Quick and Amazon Bedrock AgentCore are supported, and administrators can connect via Manage account > Permissions > AWS Agent Registry.

🔎 AWS Agent Registry is now generally available, offering a private, governed catalog and discovery layer for agents, skills, tools, MCP servers, and custom resources across organizations. It provides semantic and keyword search, a browse experience, and access via the console, AWS CLI, and AWS SDK. Registry integrates with Amazon Bedrock AgentCore, Amazon Quick, and Kiro IDE, and exposes an MCP server interface for IDE queries. New enterprise features include infrastructure-as-code support, tagging, AWS RAM sharing, auto-discovery of AgentCore runtimes, and a Quick Connectors integration.

🧭 Amazon Bedrock AgentCore Memory now supports flexible namespace variables that let developers scope long-term memories along custom application dimensions such as organization, tenant, team, or environment. Define up to five keys on a memory resource, reference them in a strategy's namespace template, and supply values at runtime via the CreateEvent API so the service substitutes them during memory extraction. The feature helps multi-tenant and complex-hierarchy applications avoid duplicate strategies and provides fine-grained control over memory organization and access. Flexible namespace variables are available today in all Regions where AgentCore Memory is generally available, at no additional cost.

🔒 Amazon Bedrock’s AgentCore Memory now supports fine-grained access control (FGAC), allowing per-user and per-tenant memory isolation via AgentCore Gateway without custom authorization code. Administrators can configure OAuth (JWT) authentication and attach Cedar policies to restrict access by caller identity, namespace claims, or specific Memory operations. The feature moves access enforcement into the infrastructure using cryptographic identity proof, and is implemented through the managed AgentCore Memory connector exposing 12 Memory operations as Cedar actions.

🚀 Amazon Bedrock AgentCore is now available in US West (N. California) and Asia Pacific (Hyderabad), enabling developers to build and run agents closer to end users. The platform supports agent runtime, identity and access control, policy management, session persistence, tool connectivity, evaluations, and observability at launch. AgentCore emphasizes secure infrastructure-level enforcement so agents cannot bypass controls. Regional availability reduces latency and improves performance for local customers.

🧭 Amazon Bedrock AgentCore Memory now accepts non-conversational JSON payloads on the CreateEvent API, enabling extraction of long-term memories from structured data. Developers can submit JSON events up to 100 KB—such as behavioral events, activity logs, and system events—without converting them into synthetic conversations. The pipeline applies all four extraction strategies: semantic, user preference, summarization, and episodic, and the feature is available now in all supported regions.

🔎 Amazon Bedrock's AgentCore Web Search now supports per-request domain filtering and published-date filtering, letting agents control which sites and time windows they search. Runtime domain filtering enables include/exclude lists for trusted or blocked sources without admin reconfiguration, while published-date filtering constrains results to specific inclusive date ranges. Admins gain gateway-level allowlists and an increased domain cap of up to 100 domains per list, and the Web Search Tool is expanding availability to eu-west-1 and ap-northeast-1.

🛡️ This post demonstrates patterns for propagating user authorization context when building AI agents with Amazon Bedrock AgentCore, ensuring each user only sees data they’re allowed to access. It explains how to embed department or custom claims in tokens via Amazon Cognito pre token generation triggers and how the AgentCore Runtime inbound JWT authorizer validates those claims before invoking agent code. The guidance shows moving enforcement into infrastructure—using STS session tags, per-request AssumeRoleWithWebIdentity for DynamoDB, metadata filters for Bedrock Knowledge Bases, and on‑behalf‑of token exchange for external SaaS—to reduce risk from compromised agents.

🔒 This post explains how to implement a request Lambda interceptor in Amazon Bedrock AgentCore Gateway to support legacy HTTP Basic Authentication for downstream tool APIs. It shows retrieving a service account credential from AWS Secrets Manager, validating inbound JWTs, and constructing a Basic Auth header while keeping credentials isolated from the agent. The article emphasizes that Basic Auth is outdated and recommends modern authentication like OAuth 2.0 or OpenID Connect, presenting this pattern only as an interim integration.

🔔 Amazon Web Services announces general availability of AgentCore payments, part of Amazon Bedrock AgentCore, enabling AI agents to discover, access, and pay for paid APIs, MCPs, and content with minimal code. The capability integrates with Coinbase and Stripe Privy wallets, supports the Machine Payment Protocol (MPP), and offers payment orchestration, configurable infrastructure-level limits, and end-to-end observability. GA features include Quick Create for Coinbase credentials, a curated Coinbase Bazar MCP server of x402 pay-per-use endpoints, and support for the x402 "upto" scheme for dynamic pricing.

🔧 The Amazon Cognito (aws-auth) skill is now included in the Agent Toolkit for AWS, enabling AI coding agents to set up, configure, secure, and troubleshoot Amazon Cognito using best-practice workflows. The skill supports user pools, app clients, OAuth 2.0 flows, token and JWT authorizer management, passkey/WebAuthn enrollment, threat protection, Lambda triggers, and identity pools. When used with the AWS MCP Server, commands run with IAM guardrails and CloudTrail audit logging; it also works standalone via the AWS CLI.

🛡️ Amazon Bedrock AgentCore is now available in AWS GovCloud (US-West), enabling regulated organizations to build context-aware agents with controls for production scale. AgentCore memory provides short-term conversational context and long-term persistent insights without complex infrastructure. Policy features let teams author natural-language policies that convert to Cedar and enforce tool access at an AgentCore gateway. The managed harness simplifies deployment by declaring models, tools, and instructions via configuration and running agents with a few API calls.

🚀 Amazon Web Services (AWS) announced general availability of runtime instances for Amazon Bedrock AgentCore, enabling agents to run on customer-managed EC2 instances without manual infrastructure management. The feature complements existing microVM-based runtimes and supports diverse EC2 families including GPU-accelerated, memory-optimized, and compute-optimized types. Runtime instances allow long-running agent sessions up to 14 days and integrate with the AWS Console, CLI, SDKs, and APIs to create capacity providers and attach agents. Availability spans multiple regions and billing includes EC2 costs plus management fees, with documentation and pricing details provided by AWS.

🛡️ Security advisories from Amazon Web Services, Google, and Vercel detail vulnerabilities in agent harnesses that allowed caller-supplied or forged tool-call data to reach execution without a verifying model turn. AWS patched its managed Bedrock AgentCore service, Google fixed ADK for Python in v2.5.0, and Vercel released fixes for its Codex and OpenCode harness packages. Each vendor's path differed in attack surface and required conditions, and mitigations focus on validating and binding tool invocations to authenticated model events.

🛡️ Amazon Bedrock AgentCore introduces temporal policies for stateful agent authorization and rate limiting to control AI traffic. Temporal policies evaluate requests in the context of prior actions within a session, enabling workflow sequencing, exact argument matching, human approvals, and data freshness checks. Rate limiting provides per-user and per-group controls via OAuth or AWS IAM to cap requests, token usage, and concurrent connections for improved downstream availability. Documentation, a blog announcement, and the Dogwood reference implementation offer regional details and guidance.

🔎 Amazon Bedrock AgentCore now sends traces, prompts, structured logs, and standard output to a single per-agent Amazon CloudWatch log group, consolidating previously separated telemetry. This removes the need to search across multiple log groups and enables scoping of IAM policies and CMK encryption at the agent level. New agents created from July 20, 2026 use this by default in supported regions; existing agents can enable it via an environment variable and ADOT 0.17.1+.

🚀 Amazon Bedrock AgentCore has increased default runtime quota limits to enable larger-scale agent workloads. The update raises active concurrent sessions to 5,000 in US East (N. Virginia) and US West (Oregon), and 2,500 in other supported Regions. All Regions now support 200 agent interactions per second and 25 new sessions per second, improving out-of-the-box throughput for agent deployments. Customers should review the AgentCore Quotas documentation and Developer Guide for details.

🚀 Amazon Bedrock AgentCore is now available in four additional AWS Regions: Asia Pacific (Bangkok), Asia Pacific (Malaysia), Europe (Milan), and Europe (Spain). AgentCore is a platform to build, connect, and optimize agents, enabling engineers to ship agents quickly with any framework and model while enforcing security at the infrastructure layer. The launch brings runtime, identity and access control, policy management, session persistence, tool connectivity, and observability to these regions, reducing latency for local end users.

🛡️ AWS Security Hub CSPM introduces the AI Security Best Practices standard, offering 31 automated controls to detect misaligned AI resources. The standard evaluates Amazon Bedrock, Bedrock AgentCore, and Amazon SageMaker workloads against recommended configurations without manual rule creation. It covers domains like network isolation, encryption, VPC placement, KMS usage, private registries, and authorization, producing findings to help teams remediate issues. Available in all Regions where Security Hub CSPM operates, including GovCloud (US) and China.

🔒 AWS announces general availability of AWS WAF protection for Amazon Bedrock AgentCore Gateway, enabling protection of agentic AI workloads from common web exploits and abuse. You can associate an AWS WAF protection pack with your AgentCore Gateway to enforce IP-based access controls, rate-based throttling, and AWS Managed Rule Groups including Bot Control. Configure protections once at the Gateway and have them applied consistently to all targets behind it.