Issue with AWS Bedrock node (Guardrail)

Questions
1

Hi,

I’d like to use the AWS Bedrock node with Guardrails in n8n, but I’ve run into two issues:

  1. to use Guardrails with Bedrock, I need to pass the parameter guardrailIdentifier. In the AWS Bedrock node, there are only two predefined options available. There is no way to add this parameter manually (e.g., as JSON). Because of this, I cannot provide my own Guardrail ID, which prevents me from using the Guardrails functionality.

  2. HTTP Request + AWS authentication – I tried working around this by using a plain HTTP Request to Bedrock. However when I selected Predefined Credential Type → AWS, I got an error saying the Authenticate header is missing: 403 - “{\“Message\”:\“Authorization header is missing\”}”. Credential is correct as it works with Bedrock node.

It looks like the request is not being properly signed (SigV4).

Questions:

  • How can I pass the guardrailIdentifier parameter in the AWS Bedrock node?

  • Is there any way to add custom JSON parameters to the Bedrock request?

  • How can I correctly configure the HTTP Request node with AWS credentials so that the Bedrock request is properly authenticated (signed)?

Thanks in advance for your help.

Information on your n8n setup

  • n8n version: 1.106.3
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: Ubuntu 24.04.2
2

Hey, in the HTTP node, have you tried using Generic Credentials that you can define yourself? Maybe this can help you move past that error.

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.