AWS in n8n: Built-in AWS Nodes vs Community Nodes

n8n has many built-in AWS nodes: S3, SQS, SNS (with a trigger), SES, Lambda, DynamoDB, Textract, Transcribe, Rekognition, Comprehend, Cognito, IAM, Certificate Manager and Elastic Load Balancing, plus the AWS Bedrock Chat Model and Embeddings AWS Bedrock for AI workflows. Community nodes fill gaps around them, such as reading from an SQS queue, prompt caching on Bedrock, Athena queries and AWS services n8n doesn’t cover. This guide covers the built-in nodes and the AWS credentials (from n8n’s documentation) and the AWS community packages on our hub (from the descriptions and READMEs their authors publish on npm, and our own download data).

Quick comparison

AWS credentials in n8n

n8n has two AWS credential types for its built-in AWS nodes:

• AWS (IAM): your Region, an Access Key ID and a Secret Access Key, created in the IAM console under your user name, Security credentials, Create access key. You can turn on Temporary security credential and add a session token, and set Custom Endpoints if n8n runs in an Amazon VPC.
• AWS (Assume Role): n8n assumes an IAM role through AWS STS and requests fresh temporary credentials when it signs requests, so you don’t manage their expiry. You enter the Role ARN, an External ID that matches the role’s trust policy and a Role Session Name (default n8n-session, shown in CloudTrail).

For the AssumeRole call itself, you either enter STS access keys or turn on Use System Credentials: on a self-hosted n8n that already has an AWS identity, n8n then reads it from environment variables, EKS IAM Roles for Service Accounts, EKS Pod Identity, an ECS or Fargate task role or an EC2 instance profile, in that order. An administrator has to set N8N_AWS_SYSTEM_CREDENTIALS_ACCESS_ENABLED=true first.

Built-in nodes worth knowing

The AWS SQS node has one operation, sending a message to a queue; it doesn’t read from one, which is why the most downloaded AWS community package is an SQS trigger. For incoming events, n8n has the AWS SNS Trigger. For AI agents, the AWS Bedrock Chat Model and Embeddings AWS Bedrock use the same AWS credentials.

AWS community nodes

Our AWS hub lists 33 packages that pass our quality rule, with 1,857 npm downloads a week between them. The most downloaded, with the description each author gives on npm (weekly npm downloads as of 28 October 2026):

Versions and dates come from the npm registry.

n8n-nodes-aws-sqs-trigger

A trigger that consumes messages from an SQS queue, using n8n’s existing AWS credential, per its short README. Its only release dates from August 2022, so test it on your n8n version before relying on it.

AWS Bedrock packages

n8n-nodes-bedrock-advanced describes itself as adding features the official Bedrock node lacks, in two nodes. AWS Bedrock Chat Model (Advanced) is a drop-in replacement with prompt caching for the system prompt, tool definitions and conversation history (5 minute or 1 hour TTL where supported), cache-aware token metrics and support for any Converse API model. Bedrock Claude adds Claude’s built-in tools (web search, computer use, bash, text editor), tool search, context compaction and streaming. n8n-nodes-aws-bedrock-assumerole runs Claude models and Nova Canvas and Titan image generation on Bedrock with AssumeRole authentication, with a chat model sub-node for AI agents; n8n’s own AWS (Assume Role) credential also covers role assumption for the built-in Bedrock Chat Model too.

Other AWS packages

• n8n-nodes-aws-sdk-v3: exposes every AWS service and operation of the JavaScript SDK, in a utilitarian way, per its README; not affiliated with AWS. Its README says it was only tested with n8n 1.45.1.
• n8n-nodes-aws-athena-query: runs SQL on Amazon Athena over data in S3 with paginated results, using signed HTTP requests and no AWS SDK.
• @cdmx/n8n-nodes-aws-s3-custom: download, upload, copy and move files in S3 with the AWS SDK v3, and lets you set credentials dynamically instead of from the credential store.
• n8n-nodes-aws-step-functions: the Step Functions API; last released in November 2023.

Check each node page here for the latest release and, where it has one, its GitHub repository for open issues before you build on a package.

How to choose

• S3, SES, SNS, Lambda, DynamoDB, Textract and the other covered services: the built-in AWS nodes.
• Keys you don’t want to store, or access across accounts: the built-in AWS (Assume Role) credential, with system credentials on AWS-hosted n8n.
• Start a workflow from an SQS queue: n8n-nodes-aws-sqs-trigger.
• Lower Bedrock costs with prompt caching, or Claude’s built-in tools: n8n-nodes-bedrock-advanced.
• Athena or a service n8n doesn’t cover: n8n-nodes-aws-athena-query, or n8n-nodes-aws-sdk-v3.

To install a package on a self-hosted instance, an owner or admin enters its npm name in Settings > Community Nodes; full steps are in How to Install n8n Community Nodes. On n8n Cloud only verified community nodes can be installed, see Verified vs Unverified n8n Community Nodes. Related: n8n Community Node Environment Variables.

FAQ

Can n8n assume an AWS IAM role?

Yes, with the AWS (Assume Role) credential: enter the Role ARN, External ID and Role Session Name, and either STS access keys or system credentials from the environment n8n runs in.

Can n8n trigger a workflow from an SQS queue?

The built-in AWS SQS node only sends messages. To read from a queue, use a community trigger such as n8n-nodes-aws-sqs-trigger.

Does n8n support AWS Bedrock?

Yes, with the built-in AWS Bedrock Chat Model and Embeddings AWS Bedrock. Community packages such as n8n-nodes-bedrock-advanced add prompt caching and Claude’s built-in tools.

What is the most used AWS community node?

n8n-nodes-aws-sqs-trigger, with 718 weekly npm downloads on 28 October 2026.