Is your feature request related to a problem? Please describe.
With Bedrock embedding models, we currently validate the model name against a supported list (like cohere.embed-v4:0). But when you run in eu-central-1 and the model isn’t available there, you end up using cross-region inference and the model id becomes something like eu.cohere.embed-v4:0. That fails the validation even though it’s the same underlying model.
Describe the solution you'd like
Either of these would solve it:
-
Support an optional inference-profile/region prefix in model ids (so eu.cohere.embed-v4:0 is accepted the same as cohere.embed-v4:0), e.g. by normalizing/stripping the prefix before comparing to supported names; or
-
Remove/relax model name validation for Bedrock embeddings and just pass through whatever model id the user provides.
Describe alternatives you've considered
N/A
Additional context
Cross-region inference docs: https://docs.aws.amazon.com/bedrock/latest/userguide/cross-region-inference.html
Is your feature request related to a problem? Please describe.
With Bedrock embedding models, we currently validate the model name against a supported list (like cohere.embed-v4:0). But when you run in eu-central-1 and the model isn’t available there, you end up using cross-region inference and the model id becomes something like eu.cohere.embed-v4:0. That fails the validation even though it’s the same underlying model.
Describe the solution you'd like
Either of these would solve it:
Support an optional inference-profile/region prefix in model ids (so eu.cohere.embed-v4:0 is accepted the same as cohere.embed-v4:0), e.g. by normalizing/stripping the prefix before comparing to supported names; or
Remove/relax model name validation for Bedrock embeddings and just pass through whatever model id the user provides.
Describe alternatives you've considered
N/A
Additional context
Cross-region inference docs: https://docs.aws.amazon.com/bedrock/latest/userguide/cross-region-inference.html