Skip to main content
Amazon Bedrock AgentCore Runtime runs your containerized agent in isolated per-session microVMs, and InvokeAgentRuntimeCommand runs shell commands inside a running session. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to aws-agentcore and these variables:
  • AGENTCORE_RUNTIME_ARN

​
Key and permissions

AGENTCORE_RUNTIME_ARN is the ARN of an existing AgentCore Runtime (agent runtime) you created; its region is taken from the ARN. AWS credentials come from the standard AWS credential chain (IAM user/role access keys, SSO, or an assumed role) created in IAM. IAM actions CostGraph calls, on the runtime ARN resource: bedrock-agentcore:InvokeAgentRuntimeCommand (create/ready/exec: a session is created implicitly by the first command on a new runtimeSessionId) and bedrock-agentcore:StopRuntimeSession (delete). There is no list call. Both permission names are stated in the AWS API/dev guide. If the runtime has a resource-based policy, it (and the endpoint policy) must also allow the caller. Sources: docs.aws.amazon.com: runtime execute command, docs.aws.amazon.com: API InvokeAgentRuntimeCommand, docs.aws.amazon.com: runtime stop session, docs.aws.amazon.com: bedrock agentcore limits, docs.aws.amazon.com: runtime lifecycle settings.

​
Limits

  • Maximum hardware allocation per session is 2 vCPU / 8 GB (not adjustable). (source)
  • Maximum session duration 8 hours on microVMs (maxLifetime 60-28800 s); idle session timeout default 15 minutes (idleRuntimeSessionTimeout up to 8 hours). Both are runtime settings, not per session. (source)
  • Per-command timeout default 300 s, max 3600 s; command max 65536 chars; runtimeSessionId at least 33 chars. (source)
  • Runtime containers must be ARM64 (arm64 only). (source)
  • Active session workloads per account: 5,000 in us-east-1/us-west-2, 2,500 elsewhere (adjustable). (source)