[Workaround] Guardrails for Bedrock Custom Model Endpoints not applied

[MarcusRosen-Rio]

Hi,

LiteLLM version: 1.60

When using a Bedrock Custom Model Endpoint the standard guardrail proxy configuration is ignored but adding headers manually from this older issue works

Works:

• model_name: DeepSeek-R1-Distill-Llama-8B
  litellm_params:
  model: bedrock/llama/arn:aws:bedrock:us-east-1:..:imported-model/...
  extra_headers: {
  "X-Amzn-Bedrock-GuardrailIdentifier": os.environ/BEDROCK_GUARDRAIL_ID_US_EAST_1,
  "X-Amzn-Bedrock-GuardrailVersion": os.environ/BEDROCK_GUARDRAIL_VERSION_US_EAST_1
  }
  aws_region_name: us-east-1

Does not work:

• model_name: DeepSeek-R1-Distill-Llama-8B
  litellm_params:
  model: bedrock/llama/arn:aws:bedrock:us-east-1:..:imported-model/..
  aws_region_name: us-east-1
  guardrailConfig: {
  "guardrailIdentifier": os.environ/BEDROCK_GUARDRAIL_ID_US_EAST_1, # The identifier (ID) for the guardrail.
  "guardrailVersion": os.environ/BEDROCK_GUARDRAIL_VERSION_US_EAST_1, # The version of the guardrail.
  "trace": "enabled", # The trace behavior for the guardrail. Can either be "disabled" or "enabled"
  }