- Newest
- Most votes
- Most comments
Hello.
"2.15.13" is an old version, so if you have a newer version, it's likely that the response will include "memoryConfiguration".
Please try upgrading your AWS CLI to the latest version by following the steps in the documentation below.
https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html
This appears to be a discrepancy between the API documentation and the actual implementation of the GetAgent API in Amazon Bedrock. While the API documentation indicates that the memoryConfiguration field should be returned as part of the Agent object when memory is configured, there seems to be an issue where this field is either null or completely absent from the response.
Based on the information available, this behavior appears to be a limitation in the current implementation of the GetAgent API. The API is not returning the memoryConfiguration field even though memory is enabled and configured for your agent via the AWS Console.
This type of inconsistency between documentation and actual API behavior has been observed in other Bedrock API operations as well. For example, there have been similar issues with the InvokeAgent API where certain parameters documented in the console aren't properly supported in the API implementation.
Unfortunately, there doesn't appear to be an alternative API specifically designed to retrieve agent memory configuration at this time. As a workaround, you might need to maintain your memory configuration settings separately for your infrastructure automation needs to prevent accidental configuration resets during agent updates.
I would recommend opening a support case with AWS to report this issue, as they would be able to confirm whether this is a known limitation or a bug that needs to be addressed. They might also be able to provide you with more specific guidance or workarounds for your use case.
Sources
Bedrock Agent API Ignores inputFiles Parameter but Console Works | AWS re:Post
MemoryConfiguration - Amazon Bedrock
able to use streamingConfigurations in AgentsforBedrockRuntime invoke_agent boto3 sdk | AWS re:Post
answered a year ago
Relevant content
- AWS OFFICIALUpdated 5 months ago

yes, the issue was the outdated CLI