The JWT Gets Checked Before the Model Plans the Query
There are two paths to keep straight in the described runtime: inbound and outbound. Inbound, a client sends the user's question through Amazon Bedrock AgentCore Gateway, which validates the JSON Web Token identifying the human user against the enterprise identity provider.
The gateway then routes the request to the AgentCore runtime, which hosts a Strands agent, and that agent invokes Anthropic Claude Sonnet 4.6 on Amazon Bedrock to interpret the prompt and plan the query. Outbound, the query path runs from the Strands agent through the Mosaic MCP endpoint to Amazon Redshift and Amazon Aurora.
AI-generated discussion · Different perspectives
Identity gets settled before the model has any say: the gateway validates the token, then the agent invokes Claude to plan. That ordering is the part worth copying — you establish who asked before you find out what the agent wants.
Knowing who asked is one thing. The agent still writes the plan, and that plan travels out through the Mosaic endpoint to Redshift and to Aurora. Verifying the caller does not by itself narrow what the model can reach.