AgentenCode evidence profileAutomation
✓ Editorially reviewedChecked: October 7, 2026
Agent profile · Automation
Amazon Bedrock AgentCore
Amazon Bedrock AgentCore is classified by AgentenCode as a agent platform from AWS. It belongs to the Automation category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.
Automationeditorial classification
AWSprovider
20 primary sourcessource status
October 7, 2026last verification
AgentenTrust 2.0 · EU & governance evidence
Trust, privacy and control evidence for Amazon Bedrock AgentCore
Direct answer: AgentenCode currently documents 7 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.
EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.
GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.
Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.
Field-level evidence
Documented controls and values from primary sources.
Documented yesDocumented valueUnknown remains unknown
High confidence
Yes — documentedAPI · Rest
AgentCore Runtime supports direct HTTP/REST invocation.
Scope: agentcore_runtime · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedAPI · Websocket
WebSocket invocation is documented for supported runtime protocols.
Scope: agentcore_runtime · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedGovernance · Audit logs · Available
AWS CloudTrail provides audit records for AgentCore Runtime API activity.
Scope: agentcore_runtime_api · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedGovernance · Logs · Cloudwatch
CloudWatch logging is documented.
Scope: agentcore_runtime · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedGovernance · Logs · Firehose Export
Firehose log export is documented.
Scope: memory_and_gateway · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedGovernance · Logs · S3 Export
S3 log destinations are documented.
Scope: memory_and_gateway · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedGovernance · Observability
Built-in observability is documented.
Scope: agentcore_resources · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedGovernance · RBAC
AgentCore access is governed through AWS IAM roles and policies.
Scope: agentcore_resources_via_aws_iam · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedHosting · Managed
Managed runtime hosting is documented.
Scope: agentcore_runtime · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedHosting · Private Network
Private VPC connectivity is documented.
Scope: gateway_targets · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedHosting · Self Hosted
AgentCore Runtime Instances provide a customer-account/VPC deployment mode in addition to serverless managed Runtime.
Scope: agentcore_runtime_instances · verified 2026-10-01 · Primary source ↗High confidence
Yes — documentedIdentity · Agent Identity
AgentCore Identity is documented as an agent identity, access and authentication management service.
Scope: agentcore_identity · verified 2026-10-03 · Primary source ↗High confidence
Yes — documentedMemory · Long Term
AgentCore long-term memory stores extracted insights across multiple sessions.
Scope: agentcore_memory_long_term · verified 2026-10-03 · Primary source ↗High confidence
Yes — documentedMemory · Session State
AgentCore short-term memory stores turn-by-turn interactions within a session.
Scope: agentcore_memory_short_term · verified 2026-10-03 · Primary source ↗High confidence
Yes — documentedMemory · Shared Across Agents
AWS documents the ability to share AgentCore memory stores across agents.
Scope: agentcore_memory_shared_stores · verified 2026-10-03 · Primary source ↗High confidence
1000Operations · Max Agents Per Account
AgentCore Runtime documents a default total limit of 1,000 agents per account.
Scope: agentcore_runtime_account_region · verified 2026-10-03 · Primary source ↗High confidence
Yes — documentedOperations · Rate Limits Documented
AWS publishes TPS/throughput limits for multiple AgentCore APIs and services.
Scope: agentcore_services · verified 2026-10-03 · Primary source ↗High confidence
Yes — documentedOperations · Service Quotas Documented
AWS publishes service/resource quotas for AgentCore Runtime, Memory, Identity, Gateway and other AgentCore services.
Scope: agentcore_services · verified 2026-10-03 · Primary source ↗Evidence-backed overview
What is Amazon Bedrock AgentCore?
Amazon Bedrock AgentCore is classified by AgentenCode as a agent platform from AWS. It belongs to the Automation category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.
Product-specific evidence for Amazon Bedrock AgentCore
This profile links 20 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.
Customer-Managed Keys
Yes · Scope: supported_agentcore_resources · verified 2026-10-01.
Primary source ↗Verschlüsselung at rest
AWS KMS (AWS owned keys) · Scope: agentcore_runtime · verified 2026-10-01.
Primary source ↗Verschlüsselung in transit
TLS 1.2+ · Scope: agentcore_runtime · verified 2026-10-01.
Primary source ↗AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.
20primary sources
32field-level evidence claims
7documented trust controls
4history events
How to read the evidence
The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.
AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.
Decision context
Provider and category
Amazon Bedrock AgentCore is documented under Automation and is associated with AWS. Category labels help navigation but do not replace product-specific evidence.
Verification status
The public profile is marked editorially reviewed and was last checked on October 7, 2026.
Trust coverage
7 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.
Source-first use
For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.
Capabilities, strengths and deployment checks for Amazon Bedrock AgentCore
Amazon Bedrock AgentCore is classified as Agent Platform from AWS. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.
Agenten produktiv betreiben
This use case is part of the stored profile for Amazon Bedrock AgentCore. The related strength is “Managed Agent Runtime”. In a production evaluation, the practical boundary to verify is: IAM-Berechtigungen eng begrenzen.
Tool- und Browsernutzung
This use case is part of the stored profile for Amazon Bedrock AgentCore. The related strength is “AWS-Integrationen”. In a production evaluation, the practical boundary to verify is: Kostenbudgets und Laufzeitlimits setzen.
Identität und Berechtigungen
This use case is part of the stored profile for Amazon Bedrock AgentCore. The related strength is “Identitäts- und Observability-Bausteine”. In a production evaluation, the practical boundary to verify is: Netzwerk- und Datenzugriffe pro Agent dokumentieren.
Monitoring agentischer Workloads
This use case is part of the stored profile for Amazon Bedrock AgentCore. The related strength is “Für produktive Agentenarchitekturen”. In a production evaluation, the practical boundary to verify is: IAM-Berechtigungen eng begrenzen.
What to verify before adoption
- IAM-Berechtigungen eng begrenzen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
- Kostenbudgets und Laufzeitlimits setzen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
- Netzwerk- und Datenzugriffe pro Agent dokumentieren. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.
Verified history
The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.
- October 7, 2026 · Product change · AWS publishes a security update for bedrock-agentcore-starter-toolkit: version 0.3.14 fixes code injection and unsafe external-reference handling affecting versions 0.1.4–0.3.13.
- October 5, 2026 · Product Status Change
- October 1, 2026 · Source Maintenance
- September 30, 2026 · New profile
Official sources
This profile links 20 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.
- AWS Docs – Amazon Bedrock AgentCore
- AWS Docs – Agent Registry record lifecycle und Namespace-Migration
- AWS Docs – AgentCore Runtime service contract
- AWS Docs – Security best practices for AgentCore Runtime
- AWS Docs – AgentCore observability
- AWS Docs – Identity and access management for AgentCore
- AWS Docs – IAM permissions for AgentCore Runtime
- AWS Docs – Deploy MCP servers in AgentCore Runtime
- AWS Docs – AgentCore Gateway VPC egress
- AWS Docs – Security model for Runtime Instances
- AWS Docs – Amazon Bedrock AgentCore overview
- AWS Docs – Add memory to your AgentCore agent
- AWS Docs – Quotas for Amazon Bedrock AgentCore
- AWS Docs – Supported AWS Regions for AgentCore
- AWS Docs – A2A protocol contract
- AWS Docs – Deploy A2A servers in AgentCore Runtime
- AWS Docs – MCP server targets in AgentCore Gateway
- AWS Docs – AgentCore Runtime authentication and authorization
- AWS Docs – Data encryption in Amazon Bedrock AgentCore
- AWS Security Bulletin 2026-127-AWS
Frequently asked questions
What is Amazon Bedrock AgentCore?
Amazon Bedrock AgentCore is listed by AgentenCode as an automation agent or agentic product from AWS.
How much trust evidence is documented for Amazon Bedrock AgentCore?
The current trust layer documents 7 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.
When was this profile last checked?
The current profile verification date is October 7, 2026. The linked primary sources remain authoritative if the product changes between checks.
Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.