Amazon Elastic Load Balancing · Arazzo Workflow

Amazon Elastic Load Balancing Add a Listener to an Existing Load Balancer

Version 1.0.0

Look up a load balancer by name and attach a new forwarding listener.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub Amazon Web ServicesHigh AvailabilityLoad BalancingNetworkingScalabilityArazzoWorkflows

Provider

amazon-elastic-load-balancing

Workflows

add-listener-to-existing-load-balancer
Resolve a load balancer by name and create a forwarding listener on it.
Chains describeLoadBalancers, createListener, and describeListeners so a new listener is added to an existing load balancer and the resulting listener set is confirmed.
3 steps inputs: listenerPort, loadBalancerName, protocol, targetGroupArn outputs: listenerArn, listeners, loadBalancerArn
1
findLoadBalancer
Resolve the load balancer ARN from its name.
2
createListener
Attach the new listener to the resolved load balancer, forwarding to the supplied target group.
3
describeListeners
List the load balancer's listeners to confirm the new one is present.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon Elastic Load Balancing Add a Listener to an Existing Load Balancer
  summary: Look up a load balancer by name and attach a new forwarding listener.
  description: >-
    Resolves an existing load balancer by name, then attaches a new listener
    that forwards to a supplied target group, and finally lists the load
    balancer's listeners to confirm the addition. This is the common flow for
    exposing an additional port (for example adding HTTPS alongside HTTP) on a
    load balancer that already exists. Each step spells out its request inline
    so the flow can be read and executed without opening the underlying OpenAPI
    description. The Elastic Load Balancing v2 API uses the AWS query protocol,
    so every operation is a GET whose inputs are carried as query parameters
    rather than a request body.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-600.50
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-600.50
      capability_name: IT Infrastructure Management
      spec: amazon-elastic-load-balancing-load-balancers-api-openapi.yml
      confidence: 0.75
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: listenersApi
  url: ../openapi/amazon-elastic-load-balancing-listeners-api-openapi.yml
  type: openapi
- name: loadBalancersApi
  url: ../openapi/amazon-elastic-load-balancing-load-balancers-api-openapi.yml
  type: openapi
workflows:
- workflowId: add-listener-to-existing-load-balancer
  summary: Resolve a load balancer by name and create a forwarding listener on it.
  description: >-
    Chains describeLoadBalancers, createListener, and describeListeners so a new
    listener is added to an existing load balancer and the resulting listener
    set is confirmed.
  inputs:
    type: object
    required:
    - loadBalancerName
    - listenerPort
    - targetGroupArn
    properties:
      loadBalancerName:
        type: string
        description: The name of the existing load balancer to add a listener to.
      protocol:
        type: string
        description: The protocol for client connections to the listener.
        default: HTTP
      listenerPort:
        type: integer
        description: The port the new listener accepts connections on.
      targetGroupArn:
        type: string
        description: The ARN of the target group the listener forwards to.
  steps:
  - stepId: findLoadBalancer
    description: Resolve the load balancer ARN from its name.
    operationId: describeLoadBalancers
    parameters:
    - name: Names
      in: query
      value: $inputs.loadBalancerName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      loadBalancerArn: $response.body#/loadBalancers/0/loadBalancerArn
  - stepId: createListener
    description: >-
      Attach the new listener to the resolved load balancer, forwarding to the
      supplied target group.
    operationId: createListener
    parameters:
    - name: LoadBalancerArn
      in: query
      value: $steps.findLoadBalancer.outputs.loadBalancerArn
    - name: Protocol
      in: query
      value: $inputs.protocol
    - name: Port
      in: query
      value: $inputs.listenerPort
    - name: DefaultActions.member.1.Type
      in: query
      value: forward
    - name: DefaultActions.member.1.TargetGroupArn
      in: query
      value: $inputs.targetGroupArn
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      listenerArn: $response.body#/listeners/0/listenerArn
  - stepId: describeListeners
    description: List the load balancer's listeners to confirm the new one is present.
    operationId: describeListeners
    parameters:
    - name: LoadBalancerArn
      in: query
      value: $steps.findLoadBalancer.outputs.loadBalancerArn
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      listeners: $response.body#/listeners
  outputs:
    loadBalancerArn: $steps.findLoadBalancer.outputs.loadBalancerArn
    listenerArn: $steps.createListener.outputs.listenerArn
    listeners: $steps.describeListeners.outputs.listeners

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/amazon-elastic-load-balancing-add-listener-to-existing-load-balancer-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.