AWS shows Okta and Bedrock AgentCore governing AI agent access for signed-in users
Overview
AWS explains how to build a task agent on Amazon Bedrock AgentCore runtime that acts for signed-in users through Okta Cross App Access and AgentCore Identity.
In AWS's example, after an administrator removed a user's assignment to the agent, Okta refused new requests within about 1 second, and issued tokens expired within 5 minutes. AWS says AgentCore Identity added about 0.6 seconds to a request that took about 30 seconds end to end.
The post is the first of two parts and provides sample code for non-production use only. AWS says the code is not a complete, deployable solution, and organizations should work with their security and legal teams to meet their own requirements before deploying it. AgentCore charges for what customers use.
Written by AI from the articles below · updated Nov 6, 12:30 PM ET
Check the sources:
Article timeline
The articles in this story. Times are ET.
- AWS Machine Learning BlogOfficialPickAWS shows how to govern AI agent access with Okta and AgentCore Identity
AIAWS explains how to build a task agent on Amazon Bedrock AgentCore runtime that acts for signed-in users through Okta Cross App Access and AgentCore Identity. The post reports that after an administrator removed a user's assignment to the agent, Okta refused new requests within about 1 second, and issued tokens expired within 5 minutes. AWS says AgentCore Identity added about 0.6 seconds to a request that took about 30 seconds end to end. The sample code is for non-production use.
Heat Trend
- Current comparable heat
- 9
- Peak comparable heat
- 10Nov 6, 1:00 PM ET
- Change in past 24 hours
- –
The trend compares only continuously observed participants, so its scope may be smaller than the current heat total. Hover or tap for hourly heat; use arrow keys with a keyboard.