Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore – Part 2
AWS Machine Learning Blog reports: In Part 1 you built one governed agent. Part 2 scales the pattern to an enterprise: Amazon Bedrock AgentCore Gateway becomes the single front door and redeems Okta's grant, Cedar policies bind each tool to the agent, a second agent runs on Amazon EKS, and AgentCore Observability traces every allow and deny beside Okta's log in Amazon CloudWatch.
Key points
- Source: AWS Machine Learning Blog
- Published: November 6, 2026
- Topics: AI Agents, Amazon, Kubernetes, Artificial Intelligence
Related articles
Serverless MCP server for AI agent data lake access on Amazon ECS Fargate
AWS Machine Learning Blog reports: Learn how to build a serverless Model Context Protocol (MCP) server on Amazon ECS with AWS Fargate that gives AI agents secure, metadata-driven access to an enterprise data lake. Exposing a new dataset requires only a JSON file, with no per-dataset integration code…
Taxonomy of agentic primitives in Amazon Quick
AWS Machine Learning Blog reports: As we built Amazon Quick, its agents grew from answering questions to taking actions, and the same primitives kept getting rebuilt under different names. This post shares the taxonomy we converged on — triggers, agents, capabilities, and learned context — found by…
SageMaker Inference now supports Multi-Instance GPU to maximize GPU utilization for model endpoints
AWS Machine Learning Blog reports: Amazon SageMaker Inference now supports GPU partitioning with NVIDIA Multi-Instance GPU (MIG), which divides one GPU into hardware-isolated partitions so you can run a different model in each or take a right-sized fraction of a newer accelerator. This post shows ho…