If your infrastructure runs on AWS, n8n is the missing automation layer that connects S3, Lambda, SES, SNS, DynamoDB, and EC2 into your workflows. Here is everything you need to know.
Why AWS + n8n?
AWS gives you raw infrastructure power. n8n gives you a visual layer to orchestrate it without writing custom code. Together they let you build sophisticated cloud automations in hours instead of days.
I have been running n8n on AWS for two years, both self-hosted on EC2 and integrated with various AWS services from n8n Cloud. Both approaches work great.
Native AWS Nodes in n8n
n8n includes native nodes for the most common AWS services: S3 (file storage), Lambda (run functions), SES (send emails), SNS (push notifications), DynamoDB (NoSQL database), and SQS (message queues). For other services, the AWS HTTP Request node lets you call any AWS API directly with proper signature authentication.
Setup: AWS Credentials
Create an IAM user in AWS with programmatic access. Attach policies for the services you will use. Generate an Access Key ID and Secret Access Key. In n8n, add AWS credentials with these keys plus your default region (us-east-1, eu-west-1, etc).
For production, use least-privilege IAM policies. Do not give your n8n user full admin access.
Top AWS Automations
1. S3 File Processing Pipeline
A file lands in an S3 bucket. n8n picks it up via webhook (using S3 event notifications + Lambda or Direct Trigger). Process the file: convert format, extract data, validate, and move to a processed folder. Upload results back to a different S3 bucket or push to a database.
2. SES Transactional Emails
Send transactional emails from your workflows via SES. Cheaper than SendGrid for high volume. n8n handles the email node configuration; SES handles delivery.
3. Lambda Function Triggers
Use n8n to orchestrate Lambda functions. Trigger Lambda from any event (webhook, schedule, database change), pass data, get results back, and continue the workflow. n8n becomes the conductor; Lambda is the specialized function executor.
4. CloudWatch Monitoring + Alerts
Pull CloudWatch metrics on a schedule. Detect anomalies (high CPU, error spikes, low disk). Send Slack or email alerts. This is a simple way to add custom monitoring without paying for Datadog.
5. DynamoDB as a Workflow Database
Use DynamoDB to store workflow state, cache API responses, or maintain user data. The DynamoDB node supports get, put, update, delete, and query operations.
Self-Hosting n8n on AWS
Running n8n on AWS yourself is straightforward. A t3.small EC2 instance ($15/month) handles dozens of workflows. Use RDS for PostgreSQL ($15-30/month) for the n8n database. Total cost: ~$30/month for production-grade automation infrastructure.
For a complete self-hosting guide, see my self-hosting tutorial. To compare with hosted alternatives, read my n8n vs Zapier comparison.
Best Practices
Use IAM roles instead of access keys when possible (especially when n8n runs on EC2). Set up VPC endpoints to keep AWS traffic within Amazon’s network. Monitor your CloudWatch billing alarms — automated workflows can rack up charges if not configured properly.
Cost Optimization
Most AWS API calls are extremely cheap (S3, SES, DynamoDB pay-per-use). The bigger cost is usually the n8n infrastructure itself. For low-volume use cases, n8n Cloud + AWS services is often cheaper than self-hosting.
Getting Started
If you have not tried n8n yet, start your free trial here. AWS nodes are available on all plans.
For more advanced setups, check my self-hosting guide and error handling best practices.