Notifications
Clear all
Topic starter
21/08/2026 4:53 pm
TL;DR: AI agents that work in notebooks often fail in production because debugging, tracing, and infrastructure management lag behind agent logic, according to Arize. The operational lesson is that agent governance now depends on continuous observability and identity-aware controls, not just model quality or deployment convenience.
NHIMG editorial — based on content published by Arize: AWS Bedrock AgentCore Observability with Arize AX
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.
Questions worth separating out
Q: How should security teams govern AI tools that can act with privileged cloud roles?
A: Security teams should govern AI tools as privileged identity paths, not as harmless application components.
Q: Why do AI agents complicate traditional access reviews?
A: AI agents complicate access reviews because they can accumulate permissions across tools and environments faster than manual certification cycles can observe.
Q: What do security teams get wrong about runtime policy for agents?
A: They often assume runtime policy alone is enough.
Practitioner guidance
- Instrument agent traces end to end Capture prompts, tool calls, model outputs, and latency in a single trace model so investigators can reconstruct every decision chain.
- Scope IAM roles to task-level access Assign each agent the smallest practical role for the exact tools and data sources it needs, then separate read-only and write-capable actions where possible.
- Minimise secrets exposed to agents Avoid persistent credentials in agent runtime where short-lived tokens or delegated access can be used instead.
What's in the full article
Arize's full article covers the implementation detail this post intentionally leaves for the source:
- Step-by-step notebook code for wiring OpenTelemetry into a Strands-based agent and exporting traces to Arize AX
- AgentCore Runtime configuration details for container creation, ECR setup, autoscaling, and IAM role provisioning
- The exact environment variables and launch parameters used to redirect observability data to Arize AX
- Trace view and agent graph workflows that show how to inspect tool calls, latency, cost, and failure patterns
👉 Read Arize's walkthrough of production observability for AI agents on AWS Bedrock AgentCore →
AI agent observability at scale: what IAM and security teams need?
Explore further
21/08/2026 5:11 pm
Observability is becoming an identity governance control, not just an engineering convenience. When AI agents can call tools, retrieve data, and execute actions in production, traceability becomes part of authorisation. The article shows a runtime pattern where OpenTelemetry and OpenInference turn execution into evidence. That aligns with broader NHI governance because an agent is effectively a non-human workload identity with behavioural drift potential. Practitioners should treat trace completeness as a prerequisite for trust.
A question worth separating out:
Q: Who should own AI agent governance in an enterprise identity programme?
A: Ownership should sit with identity and security teams, not with model governance alone, because the operational risk comes from credentials, privilege, and runtime enforcement. The accountable team must be able to see the agent identity, scope its access, and retire it when the workflow changes.
👉 Read our full editorial: Operational observability for AI agents changes production governance
