Amazon Elastic Load Balancing · Arazzo Workflow

Amazon Elastic Load Balancing Decommission a Load Balancer

Version 1.0.0

Resolve a load balancer by name, inventory its listeners, then delete it.

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

Provider

amazon-elastic-load-balancing

Workflows

decommission-load-balancer
Inventory a load balancer's listeners and then delete the load balancer.
Chains describeLoadBalancers, describeListeners, deleteLoadBalancer, and a confirming describeLoadBalancers so a named load balancer is removed and its absence verified.
4 steps inputs: loadBalancerName outputs: deletedListeners, deletedLoadBalancerArn
1
findLoadBalancer
Resolve the load balancer ARN from its name.
2
inventoryListeners
List the listeners that will be deleted along with the load balancer for the decommission record.
3
deleteLoadBalancer
Delete the load balancer, which also deletes its listeners.
4
confirmGone
Confirm the deleted load balancer no longer appears in the account.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon Elastic Load Balancing Decommission a Load Balancer
  summary: Resolve a load balancer by name, inventory its listeners, then delete it.
  description: >-
    Tears down a load balancer cleanly. It resolves the load balancer by name,
    inventories the listeners that will be removed alongside it for the audit
    trail, deletes the load balancer, and confirms it no longer appears. 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: decommission-load-balancer
  summary: Inventory a load balancer's listeners and then delete the load balancer.
  description: >-
    Chains describeLoadBalancers, describeListeners, deleteLoadBalancer, and a
    confirming describeLoadBalancers so a named load balancer is removed and its
    absence verified.
  inputs:
    type: object
    required:
    - loadBalancerName
    properties:
      loadBalancerName:
        type: string
        description: The name of the load balancer to decommission.
  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: inventoryListeners
    description: >-
      List the listeners that will be deleted along with the load balancer for
      the decommission record.
    operationId: describeListeners
    parameters:
    - name: LoadBalancerArn
      in: query
      value: $steps.findLoadBalancer.outputs.loadBalancerArn
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      listeners: $response.body#/listeners
  - stepId: deleteLoadBalancer
    description: Delete the load balancer, which also deletes its listeners.
    operationId: deleteLoadBalancer
    parameters:
    - name: LoadBalancerArn
      in: query
      value: $steps.findLoadBalancer.outputs.loadBalancerArn
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      deleted: $statusCode
  - stepId: confirmGone
    description: Confirm the deleted load balancer no longer appears in the account.
    operationId: describeLoadBalancers
    parameters:
    - name: Names
      in: query
      value: $inputs.loadBalancerName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      remaining: $response.body#/loadBalancers
  outputs:
    deletedLoadBalancerArn: $steps.findLoadBalancer.outputs.loadBalancerArn
    deletedListeners: $steps.inventoryListeners.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-decommission-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.