{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-08T16:32:29.298Z",
  "record_id": "VXI-EXT-AWS-AC-SEC-01-v1",
  "record_kind": "external_reference",
  "title": "Amazon Bedrock AgentCore: Credentials inside the execution boundary",
  "system": "Amazon Bedrock AgentCore",
  "evidence_family": "agent_security",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an isolated agent runtime hide its execution-role credentials from code running inside it?",
  "near_questions": [
    "Can sandboxed agent code access its AWS role?",
    "Which credentials remain available inside an agent VM?",
    "Does private networking hide runtime credentials?",
    "What permissions should an agent execution role have?",
    "Does runtime isolation remove credential exposure?",
    "Can generated code use runtime permissions?",
    "Which role grants an agent access to AWS resources?",
    "What changes when the execution role changes?",
    "Is isolation separate from least privilege?",
    "What credential evidence should a runtime review retain?",
    "Does a sandbox prove an agent cannot access data?",
    "Can runtime credentials exceed the invoking user's authority?"
  ],
  "supported_claims": [
    {
      "claim": "AWS documents that code inside an AgentCore VM can obtain execution-role credentials through its metadata service, independently of network mode. The role therefore needs permissions limited to the intended operations. Runtime isolation does not establish that code inside the VM cannot use those credentials.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "credential secrecy from code inside the VM",
    "verified permissions in a buyer deployment",
    "authorisation of every generated action"
  ],
  "public_summary": "AWS documents that code inside an AgentCore VM can obtain execution-role credentials through its metadata service, independently of network mode. The role therefore needs permissions limited to the intended operations. Runtime isolation does not establish that code inside the VM cannot use those credentials.",
  "related_record_ids": [
    "VXI-EXT-AWS-AC-SEC-02-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Understanding Credentials Management in Amazon Bedrock AgentCore",
    "source_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/security-credentials-management.html",
    "checked_on": "2026-10-08",
    "candidate_record_id": "VXI-EXT-AWS-AC-SEC-01-v1",
    "candidate_record_sha256": "ebda4545b1e523005bc4fb8a00e7cba23d7a6b4fb6152a80749b08f7f4dfae38",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "AWS documents that code inside an AgentCore VM can obtain execution-role credentials through its metadata service, independently of network mode. The role therefore needs permissions limited to the intended operations. Runtime isolation does not establish that code inside the VM cannot use those credentials.",
    "required_buyer_context": "The AgentCore service, execution-role policy, invoking principals, code executed inside the VM and intended resource operations. This reference does not inspect that deployment.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "evidence_receipt",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#aws-agentcore-execution-role-credentials",
  "machine_readable_record": "/varexis-index/records/aws-agentcore-execution-role-credentials.json"
}
