AWS ELB n8n INTEGRATION: AUTOMATE AWS ELB WITH N8N

This action retrieves a list of all load balancers in your AWS account, making it perfect for inventory management, monitoring dashboards, or workflows that need to iterate over your entire load balancer fleet. Instead of querying each load balancer individually, you can pull the complete list in a single operation.

Key parameters: Credential to connect with (required): Select the AWS IAM account to authenticate with. This dropdown lists all configured AWS credentials in your n8n instance. Resource: Fixed to "Load Balancer"—this specifies you're working with ELB resources. Operation: Fixed to "Get Many"—indicates bulk retrieval. Return All: A toggle that determines whether to fetch every load balancer or respect the limit parameter. Enable this for complete inventory pulls; disable it when you only need a sample. Limit: When "Return All" is disabled, this numeric field caps the number of results. Useful for pagination or when you only need the first few entries.

Use cases: Build a daily inventory report of all load balancers sent to Slack or email, feed load balancer data into a monitoring workflow that checks health status, or sync your load balancer list to an external CMDB or documentation system.

When you need detailed information about a specific load balancer—its configuration, state, DNS name, or attached listeners—this action delivers exactly that. It's the go-to choice when your workflow already knows which load balancer to target.

Key parameters: Credential to connect with (required): The AWS IAM account for authentication. Resource: Fixed to "Load Balancer". Operation: Fixed to "Get"—single resource retrieval. Load Balancer ARN (required): The Amazon Resource Name identifying the specific load balancer. This text field accepts the full ARN string (e.g., arn:aws:elasticloadbalancing:us-east-1:123456789:loadbalancer/app/my-alb/abc123).

Use cases: Fetch configuration details before modifying a load balancer in subsequent workflow steps, verify a load balancer exists before attempting certificate operations, or pull DNS names dynamically for use in DNS update workflows.

This action permanently removes a load balancer from your AWS account. It's essential for cleanup workflows, decommissioning processes, or cost optimization automations that remove unused resources.

Key parameters: Credential to connect with (required): AWS IAM credentials with delete permissions. Resource: Fixed to "Load Balancer". Operation: Fixed to "Delete". Load Balancer ARN (required): The ARN of the load balancer to delete. Double-check this value—deletion is irreversible.

Use cases: Automatically clean up load balancers for terminated environments (dev, staging, feature branches), remove load balancers flagged as unused by a cost optimization workflow, or decommission infrastructure as part of an automated offboarding process.

The counterpart to adding certificates, this action detaches a certificate from a listener. Essential for certificate rotation workflows, decommissioning domains, or cleaning up expired certificates.

Key parameters: Credential to connect with (required): AWS IAM credentials. Resource: Fixed to "Listener Certificate". Operation: Fixed to "Remove". Load Balancer ARN Name or ID (required): The ARN or ID of the parent load balancer. Listener ARN Name or ID (required): The ARN or ID of the listener. Certificate ARN (required): The ARN of the certificate to remove.

Use cases: Remove expired certificates after rotation is complete, clean up certificates for domains no longer in use, or automate certificate lifecycle management alongside ACM events.

This action provisions a new load balancer with your specified configuration. It's the foundation for infrastructure-as-code workflows, auto-scaling architectures, and dynamic environment provisioning.

Key parameters: Credential to connect with (required): AWS IAM credentials with creation permissions. Name (required): The name for your new load balancer. Choose something descriptive that follows your naming conventions. IP Address Type (required): Select ipv4 or dualstack (IPv4 + IPv6). Schema (required): Choose Internet Facing (public) or Internal (private)—this determines network accessibility. Type (required): The load balancer type: Application (Layer 7), Network (Layer 4), or Gateway. Subnet ID Names or IDs (required): Comma-separated subnet IDs where the load balancer will be deployed. Ensure subnets span multiple availability zones for high availability. Additional Fields: Optional extra configurations for advanced setups.

Use cases: Spin up a new Application Load Balancer when deploying a new microservice, create Network Load Balancers dynamically for high-throughput services, or provision complete environments (load balancer + related resources) from a single trigger.

This action attaches an SSL/TLS certificate to an existing listener, enabling HTTPS traffic or adding additional certificates for SNI (Server Name Indication). It's critical for certificate rotation workflows and multi-domain setups.

Key parameters: Credential to connect with (required): AWS IAM credentials. Resource: Fixed to "Listener Certificate". Operation: Fixed to "Add". Load Balancer ARN Name or ID (required): The ARN or ID of the load balancer containing the listener. Listener ARN Name or ID (required): The ARN or ID of the specific listener to modify. Certificate ARN (required): The ARN of the ACM certificate to attach. This certificate must already exist in AWS Certificate Manager.

Use cases: Automatically add new certificates when issued by ACM or a third-party CA, implement zero-downtime certificate rotation by adding new certs before removing old ones, or add domain-specific certificates for SNI configurations.

This action retrieves all certificates attached to a listener, providing visibility into your SSL/TLS configuration. It's useful for auditing, compliance checks, and pre-flight validation before certificate operations.

Key parameters: Credential to connect with (required): AWS IAM credentials. Resource: Fixed to "Listener Certificate". Operation: Fixed to "Get Many". Load Balancer ARN Name or ID (optional): Optionally filter by load balancer. Listener ARN Name or ID (optional): Optionally filter by listener. Return All (optional): Toggle to return all certificates or respect the limit. Limit (optional): Maximum number of certificates to return. Defaults to 100.

Use cases: Audit all certificates across your load balancers for expiration dates, verify certificate attachment before removing the old certificate during rotation, or generate compliance reports showing which certificates are in use.