Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

LocalStack's Bedrock Runtime emulation returns the latencyMs field in the ConverseMetrics as a floating-point number, which causes deserialization errors in AWS SDKs that expect an integer value according to the official AWS Bedrock API specification.

Environment
LocalStack version: 4.5.0 (Pro)
Service: bedrock-runtime
API: Converse
Backend: Ollama integration

LocalStack returns:
{ "metrics": { "latencyMs": 3293214.919 } }

Expected Behavior

According to the AWS Bedrock Runtime Converse API documentation, the latencyMs field should be an integer representing milliseconds.

Should return:
{ "metrics": { "latencyMs": 3293214 } }

How are you starting LocalStack?

With a docker-compose file

Steps To Reproduce

-Set up LocalStack Pro with Bedrock Runtime enabled
-Configure Ollama backend
-Make a Converse API call using any AWS SDK
-Observe deserialization failure due to floating-point latencyMs

Environment

OS: macOS

LocalStack version: 4.5.0
LocalStack Docker image sha: sha256:1648217219da3f90e6ad1841921089cffa9aa703e25bc5cb9f7a579301d01650
LocalStack build date: 2025-06-05
LocalStack build git hash: 6baf98bf2

Anything else?

No response