AWS adds a managed consent portal for agents acting on a user's behalf

When an agent needs to act inside a third-party service for a particular person, such as reading a calendar or filing a ticket, that person usually has to grant access through an OAuth consent flow. AWS said developers have had to build and host the callback infrastructure for that flow on their own. The new portal is a managed version of it.

According to the announcement, platform administrators can share a portal address with their teams before any agent session starts, so that consent for outside tools is already in place when work begins. Users can later check the status of their connections through a self-service page without going to an administrator.

AWS said the portal is available in all commercial regions where AgentCore Identity is offered. For organizations, the feature puts user consent for agent access in one managed place instead of in separate flows built for each application, which makes it easier to see which person allowed which agent to reach which service.