Resources · n8n integration

AWS ELB n8n integrationAutomate AWS ELB with n8n.

Load balancers are rarely worth clicking through a console for. The AWS ELB n8n integration puts 7 operations behind one node, across 2 resources, so creating a load balancer, listing what already runs and rotating listener certificates all happen inside a workflow. Built for ops and platform teams.

Try the AWS ELB integration on n8nSee the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the AWS ELB n8n integration actually do?

It lets a workflow create, read and delete load balancers, and manage the certificates attached to their listeners, without anyone opening the AWS console. The node ships with n8n and exposes 7 operations split over 2 resources, Load Balancer and Listener Certificate. It runs on an AWS credential, meaning a set of login details saved once in n8n and reused by every workflow that needs it.

Start with the routine audit. A Schedule Trigger fires every morning, loadBalancer.getMany returns the load balancers AWS knows about, and the rows land in Google Sheets where the ops team reads them without an AWS console login. Switch Return All on and n8n walks every page of the API response instead of stopping at Limit.

Certificate rotation is the second one. When a replacement certificate is ready, listenerCertificate.add attaches it to the HTTPS or TLS listener, listenerCertificate.getMany reads the list back so the workflow can check what is really in place, and listenerCertificate.remove takes out the entry nobody needs anymore. The run posts its result to Slack.

Provisioning is the third. A merge in GitHub can start a workflow that runs loadBalancer.create with the name, type and subnets of a new environment, then loadBalancer.get to read the record back, and loadBalancer.delete once that environment is torn down.

The catalogue stops at 7 operations across 2 resources. Anything outside it goes through the HTTP Request node, which calls any endpoint of the AWS ELB API and reuses the same AWS credential through predefined authentication.

There is no AWS ELB trigger node in n8n, so a workflow around it starts somewhere else: a Schedule Trigger on a fixed interval, an n8n Webhook (a URL another service calls to launch the run), or the trigger of another tool. The n8n review covers how that choice plays out day to day, and the n8n training walks through building these workflows end to end.

Connect

How do you connect AWS ELB to n8n?

  1. 01

    Create the access key in AWS

    Log in to the IAM console, open your user name in the navigation bar and select Security credentials. In the Access keys section, select Create access key, choose your use case (or Other if nothing is proposed), and set a description tag such as n8n integration so the key is easy to recognize later. Then reveal the Access Key ID and the Secret Access Key.

  2. 02

    Save the AWS credential in n8n

    In n8n, open the Credentials menu and add an AWS (IAM) credential. Select your Region, then paste the Access Key ID and the Secret Access Key you just revealed. A credential is created once and reused: every workflow that touches AWS ELB picks it from a dropdown instead of carrying its own keys.

  3. 03

    Point the AWS ELB node at it

    Add the AWS ELB node to a workflow and choose the credential in its list. If static keys are not an option, use the AWS (Assume Role) credential type instead: it authenticates by assuming an IAM role through AWS STS, with the keys for the AssumeRole call either typed in or read automatically from the environment n8n runs in.

Actions

The 7 operations of the AWS ELB node

The AWS ELB node exposes 7 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetDeleteAddRemoveGet Many
Listener Certificate✓✓✓
Load Balancer✓✓✓✓

Listener Certificate

3 operations
01

Add a listener certificate

listenerCertificate.add

What you see in n8n

Notes & use cases

This operation adds an SSL server certificate to the certificate list of an HTTPS or TLS listener, so that listener can serve traffic for the matching domain.

Key parameters

  • Load Balancer ARN Name or ID: the load balancer that owns the listener. Pick it from the list, or feed the identifier with an expression, the n8n syntax that reads a field from the incoming item, such as {{ $json.loadBalancerId }}.
  • Listener ARN Name or ID: the listener that receives the certificate, chosen from the list or set by expression.
  • Certificate ARN: the unique identifier of the certificate to attach, as text.
Use cases
a renewal workflow attaches this year's certificate to the public listener before the current one expires.
02

Get many listener certificates

listenerCertificate.getMany

What you see in n8n

Notes & use cases

Reading back what a listener actually serves starts here. The operation returns the certificates currently attached to one listener.

Key parameters

  • Load Balancer ARN Name or ID and Listener ARN Name or ID: the pair that identifies which listener to inspect.
  • Return All: on, n8n pages through the whole certificate list; off, Limit caps how many certificates come back.
Use cases
a weekly check lists the certificates on each public listener and flags the ones that should already have been replaced.
03

Remove a listener certificate

listenerCertificate.remove

What you see in n8n

Notes & use cases

Once a replacement is live, the old entry stays in the listener's certificate list until something takes it out. That is what this operation does.

Key parameters

  • Load Balancer ARN Name or ID: the load balancer in front of the listener.
  • Listener ARN Name or ID: the HTTPS or TLS listener to clean up.
  • Certificate ARN: the identifier of the certificate leaving the list, often carried over from an earlier node as {{ $json.certificateId }}.
Use cases
the second half of a rotation, run only after Get Many has confirmed the new certificate is attached.

Load Balancer

4 operations
04

Create a load balancer

loadBalancer.create

What you see in n8n

Notes & use cases

Here the node creates the load balancer itself, with the settings AWS needs before it can exist.

Key parameters

  • Name: unique per region per account, up to 32 characters.
  • Type: application or network.
  • Schema: internal or internet-facing.
  • IP Address Type: ipv4 or dualstack, the addressing used by the subnets.
  • Subnet ID Names or IDs: the subnets it sits in, from the list or by expression.
  • Additional Fields: Security Group IDs and Tags.
Use cases
spinning up the entry point of a staging environment from a single workflow run.
05

Delete a load balancer

loadBalancer.delete

What you see in n8n

Notes & use cases

One value is enough to remove a load balancer: the identifier of the one that should go.

Key parameters

  • Load Balancer ARN: the unique identifier of the load balancer to delete, typed in as text or built from an earlier node with {{ $json.loadBalancerId }}.
Use cases
the teardown half of an ephemeral environment. The workflow that created the load balancer stores its identifier, and a later run passes that same value here so nothing keeps billing quietly in the background.
06

Get a load balancer

loadBalancer.get

What you see in n8n

Notes & use cases

One load balancer, one lookup. The operation returns the record behind a single identifier, which is what you want before acting on it.

Key parameters

  • Load Balancer ARN: the unique identifier of the load balancer to read, as text.
Use cases
right after a create step, to read back the freshly created load balancer and push its details into a ticket or a runbook page, so the team sees what was provisioned without going to AWS.
07

Get many load balancers

loadBalancer.getMany

What you see in n8n

Notes & use cases

No required field on this one. The node lists load balancers and hands them to the next step of the workflow.

Key parameters

  • Return All: on, every page of results comes back; off, Limit sets the maximum number of load balancers returned.
  • Filters: Names narrows the result to specific load balancer names, several separated by a comma.
Use cases
the daily inventory that feeds a spreadsheet, or a filtered lookup by name when only one environment matters.
Need help

Need help automating AWS ELB with n8n?

A person reads every message.

FAQ

AWS ELB and n8n: common questions

01Is the AWS ELB n8n integration free?
Yes, on the n8n side. The AWS ELB node ships with n8n, so there is nothing to install and nothing extra to pay for it, whether you run n8n Cloud or a self-hosted instance (Community Edition, under the Sustainable Use license). The same 7 operations are available in both cases, and a workflow built on one runs identically on the other. What AWS itself charges for the load balancers you create is a separate matter, decided by your AWS account and not by n8n. The node only calls the AWS ELB API on your behalf with the credential you saved.
02Which AWS credentials does the node need?
Two credential types work with this node. AWS (IAM) authenticates with an access key: you select your Region, then enter the Access Key ID and the Secret Access Key generated in the IAM console. If the key is temporary, turn on Temporary security credential and add the Session token. AWS (Assume Role) takes a different route and authenticates by assuming an IAM role through AWS STS, with the keys used for the AssumeRole call either entered by hand or read automatically from the environment n8n runs in. If you self-host n8n on EKS, ECS or EC2, AWS system credentials let you avoid storing static keys in n8n.
03What are the limits of the AWS ELB node?
The node covers 7 operations across 2 resources, Load Balancer and Listener Certificate. It supports creating and managing application and network load balancers, and does not currently support gateway load balancers. Anything the catalogue does not include goes through the HTTP Request node, which calls any endpoint of the AWS ELB API and reuses the same AWS credential through predefined authentication, so you stay in one workflow. On the two list operations, remember that Return All is what pages through the full result set, while leaving it off caps the response at Limit.
04Can a workflow react to AWS ELB in real time?
Not from AWS ELB itself: there is no AWS ELB trigger node in n8n, so nothing here listens for changes. A workflow around this node starts somewhere else. A Schedule Trigger runs it on a fixed interval, which fits inventories, certificate checks and daily reports. An n8n Webhook, meaning a URL that another service calls, starts the run when your own tooling decides something happened. Or the trigger of another tool kicks things off, for example a merge in a repository or a message in a chat channel. From there the AWS ELB node does its work as a regular step.
05n8n or Make for AWS ELB?
It depends on where you want the automation to live. Make is a hosted automation platform with no self-hosting option and billing per operation, so the cost follows how many steps your scenarios run. n8n can be self-hosted with Docker or npm, or used on n8n Cloud, and a workflow behaves the same either way. For AWS ELB specifically, the hosting question tends to decide it: teams that keep infrastructure tooling inside their own network usually want the self-hosted option and the control over data that comes with it. Both offer visual workflow building, so try the one that matches your hosting constraints first.
Same platform

Other docs you might need on this stack.

Browse all integrations