- Newest
- Most votes
- Most comments
Hello.
What version of boto3 are you using?
I was able to reproduce the error in my environment, but the version of boto3 I was using was "1.37.22".
I used the latest version (1.38.19) as of May 2025 and confirmed that the code could be executed without errors.
If you are using an older version of boto3, try updating to a newer version.
The code used for testing is the following:
import boto3
import json
client = boto3.client("bedrock-runtime")
system = [{ "text": "You are a helpful assistant" }]
messages = [
{
"role": "user",
"content": [
{
"text": "Write a short story about dragons"
},
{
"cachePoint": {
"type": "default"
}
}
]
},
]
inf_params = {"maxTokens": 300, "topP": 0.1, "temperature": 0.3}
additionalModelRequestFields = {
"inferenceConfig": {
"topK": 20
}
}
model_response = client.converse(
modelId="us.amazon.nova-lite-v1:0",
messages=messages,
system=system,
inferenceConfig=inf_params,
additionalModelRequestFields=additionalModelRequestFields
)
print("\n[Full Response]")
print(json.dumps(model_response, indent=2))
print("\n[Response Content Text]")
print(model_response["output"]["message"]["content"][0]["text"])
I apologize, but there seems to be a misunderstanding in your question. Based on the available information about the Amazon Bedrock Runtime and the Converse API for Amazon Nova Lite, there is no direct support for a "cachePoint" parameter or prompt caching in the way you've described.
The error you're encountering, "Unknown parameter in messages[0].content[1]: cachePoint", suggests that you're trying to use a parameter that is not recognized by the API for this model.
For the Amazon Nova Lite model (amazon.nova-lite-v1:0) using the Converse API, the standard parameters you can use include:
- modelId: Specifies the model to use (in this case, "amazon.nova-lite-v1:0")
- messages: An array of message objects representing the conversation
- inferenceConfig: Contains parameters like maxTokens, temperature, and topP
The Converse API for Amazon Nova does not have a built-in parameter for prompt caching as described in your question. The prompt caching guide you referenced is likely for a different service or API.
To rectify the error, you should remove the "cachePoint" parameter from your API call. If you need to optimize performance or reduce latency, you might want to look into other AWS services or caching strategies at the application level, rather than trying to use a non-existent parameter in the Converse API call.
Here's an example of a correct Converse API call for Amazon Nova Lite:
response = client.converse( modelId="amazon.nova-lite-v1:0", messages=[ { "role": "user", "content": [{"text": "Your message here"}] } ], inferenceConfig={ "maxTokens": 512, "temperature": 0.5, "topP": 0.9 } )
This should resolve the ParamValidationError you're encountering. Remember to adjust the inferenceConfig parameters as needed for your specific use case.
Sources
Using the Converse API - Amazon Nova
Amazon Bedrock Runtime examples using SDK for Python (Boto3) - AWS SDK Code Examples
Invoke Amazon Nova on Amazon Bedrock using Bedrock's Converse API - AWS SDK Code Examples
Invoke Amazon Nova on Amazon Bedrock using Bedrock's Converse API - Amazon Bedrock
answered a year ago
supported-models lists
amazon.nova-lite-v1:0But, getting startedExample requestdoes not include sample request for theamazon.nova-lite-v1:0model
Relevant content
asked a year ago
asked 3 years ago
- AWS OFFICIALUpdated 5 months ago

thank you @riku I had updated boto3 to latest 1.38.19 & was able to test a prompt-caching py using the model
anthropic.claude-3-7-sonnet-20250219-v1:0but, while setting up a new venv, got the below warning:aiobotocore 2.22.0 requires botocore<1.37.4,>=1.37.2, but you have botocore 1.38.19 which is incompatible. I tried to upgrade the packageaiobotocore, it reset boto3 & botocore to 1.37I checked this in my environment, and I think the latest version of boto3 cannot be used due to version dependencies. https://pypi.org/project/aiobotocore/
There is also discussion about the botocore version in the following GitHub issue, so I expect it will probably be addressed soon. https://github.com/aio-libs/aiobotocore/issues/1318