Question

A developer is building a Bedrock Agent for an airline that helps customers rebook flights. The agent's action group Lambda needs the authenticated customer's loyalty tier and preferred language on every turn so the model tailors its responses, but this data must NOT be exposed to the foundation model as part of the conversation the user can see, and it must persist for the duration of the conversation without being re-sent by the client on each request. Which mechanism should the developer use when invoking the agent?

Accepted Answer

Pass the loyalty tier and language as sessionAttributes in the InvokeAgent sessionState, which persist across turns in the session and are available to the Lambda but not injected into the model prompt

Answer

Pass the values as promptSessionAttributes in sessionState so they are automatically substituted into the orchestration prompt template on every turn

Answer

Include the loyalty tier and language in the inputText of each InvokeAgent call so the model has full context

Answer

Store the values in the action group's OpenAPI schema as default parameter values so they are sent to the Lambda automatically