Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

Kong 3.9.0

Current Behavior

When using AWS Bedrock inference profiles, which are formatted as: arn:aws:bedrock:us-east-1:<account_id>:application-inference-profile/<profile_id>, kong is unable to route the request.
I have experience two behaviors:

1. if the ai-proxy is configured with the unescaped ARN, Kong fails with:

{"error":{"message":"transformation failed from type bedrock://llm/v1/chat: no generation candidates received from Bedrock, or max_tokens too short"}}

2. when configured with the escaped one (arn%3Aaws%3Abedrock%3Aus-east-1%3A<account_id>%3Aapplication-inference-profile%2F<profile_id>), Kong fails with:

{"message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method."}

Expected Behavior

Kong should correctly format and escape the ARN when generating the SigV4 signature and constructing the request URL to match AWS’s expected format.

• The Converse API requires the URL to be formatted as:

  /model/<model-id/inference-profile>/converse
  

• The AWS CLI (in debug mode) shows that this URL is then encoded when making the request to Bedrock.

Steps To Reproduce

1. Create the plugin with the unescaped model_name ARN

   • Example configuration (following the kong documentation):

     curl -X POST http://localhost:8001/services/bedrock-service/plugins \
      --header 'Content-Type: application/json' \
      --header 'accept: application/json' \
      --data '{
      "name": "ai-proxy",
      "instance_name": "ai-proxy-bedrock",
      "config": {
        "route_type": "llm/v1/chat",
        "auth": {
          "allow_override": false,
          "aws_access_key_id": "<YOUR_AWS_ACCESS_KEY_ID>",
          "aws_secret_access_key": "<YOUR_AWS_SECRET_ACCESS_KEY>"
        },
        "model": {
          "provider": "bedrock",
          "name": "arn:aws:bedrock:us-east-1:<account_id>:application-inference-profile/<profile_id>",
          "options": {
            "bedrock": {
              "aws_region": "us-east-1"
            }
          }
        }
      }
      }'
     

     This will fail with the transformation error reported above.

2. Create the plugin with the escaped model_name ARN

   • Example configuration (following the kong documentation):

     curl -X POST http://localhost:8001/services/bedrock-service/plugins \
      --header 'Content-Type: application/json' \
      ...
          "provider": "bedrock",
          "name": "arn%3Aaws%3Abedrock%3Aus-east-1%3A<account_id>%3Aapplication-inference-profile%2F<profile_id>",
      ...
      }'
     

     This will fail with the sigv4 error.

Anything else?

• I did check the aws cli with the inference profile to rule out authentication errors with the inference profile, and the profile works using the converse endpoint.
• I verified the URL behavior by enabling the File Log plugin on /dev/stdout.