Problem Statement
This issue also exist with AgentCore memory
There are a couple issues with the S3SessionManager:
- There is no way to pass an S3SessionManager into the class. A new boto3 s3 client is created every single time.
- The sessionManager class is tied to a sessionId upon initialization. There is no way to update it afterwards. It means there is no way to save a singleton class.
These issue results in added latency for every single agent conversation turn and should be considered anti-patterns.
Proposed Solution
- Let client pass in an S3 client, only create a new one if None is passed in
- Allow the S3SessionManager to be used as a singleton and can be invoked/set to different sessionIds
Use Case
Using strands with S3Session manager or AgentCore memory
Alternatives Solutions
No response
Additional Context
No response
Problem Statement
This issue also exist with AgentCore memory
There are a couple issues with the S3SessionManager:
These issue results in added latency for every single agent conversation turn and should be considered anti-patterns.
Proposed Solution
Use Case
Using strands with S3Session manager or AgentCore memory
Alternatives Solutions
No response
Additional Context
No response