Amazon Elastic Load Balancing · Arazzo Workflow

Amazon Elastic Load Balancing Register Targets and Check Health

Version 1.0.0

Create a target group, register a target, then read back its health state.

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

Provider

amazon-elastic-load-balancing

Workflows

register-targets-and-check-health
Create a target group, register a target, and describe its health.
Chains createTargetGroup, registerTargets, and describeTargetHealth so a newly created target group is populated and its health surfaced in one run.
3 steps inputs: port, protocol, targetGroupName, targetId, vpcId outputs: healthState, targetGroupArn
1
createTargetGroup
Create the target group that will hold the registered target.
2
registerTargets
Register the supplied target with the new target group.
3
describeTargetHealth
Read back the health of the registered target.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon Elastic Load Balancing Register Targets and Check Health
  summary: Create a target group, register a target, then read back its health state.
  description: >-
    A focused flow for onboarding a backend target into a load balancer. It
    creates an HTTP target group, registers the supplied target with it, and
    immediately reads the target health so the caller can see the initial
    state. 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
sourceDescriptions:
- name: targetGroupsApi
  url: ../openapi/amazon-elastic-load-balancing-target-groups-api-openapi.yml
  type: openapi
- name: targetsApi
  url: ../openapi/amazon-elastic-load-balancing-targets-api-openapi.yml
  type: openapi
workflows:
- workflowId: register-targets-and-check-health
  summary: Create a target group, register a target, and describe its health.
  description: >-
    Chains createTargetGroup, registerTargets, and describeTargetHealth so a
    newly created target group is populated and its health surfaced in one run.
  inputs:
    type: object
    required:
    - targetGroupName
    - vpcId
    - targetId
    properties:
      targetGroupName:
        type: string
        description: The unique name for the target group.
      vpcId:
        type: string
        description: The ID of the VPC for the target group.
      protocol:
        type: string
        description: The protocol for routing traffic to the targets.
        default: HTTP
      port:
        type: integer
        description: The port the targets receive traffic on.
        default: 80
      targetId:
        type: string
        description: The ID of the target to register (instance ID, IP, or Lambda ARN).
  steps:
  - stepId: createTargetGroup
    description: Create the target group that will hold the registered target.
    operationId: createTargetGroup
    parameters:
    - name: Name
      in: query
      value: $inputs.targetGroupName
    - name: Protocol
      in: query
      value: $inputs.protocol
    - name: Port
      in: query
      value: $inputs.port
    - name: VpcId
      in: query
      value: $inputs.vpcId
    - name: HealthCheckProtocol
      in: query
      value: $inputs.protocol
    - name: TargetType
      in: query
      value: instance
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      targetGroupArn: $response.body#/targetGroups/0/targetGroupArn
  - stepId: registerTargets
    description: Register the supplied target with the new target group.
    operationId: registerTargets
    parameters:
    - name: TargetGroupArn
      in: query
      value: $steps.createTargetGroup.outputs.targetGroupArn
    - name: Targets.member.1.Id
      in: query
      value: $inputs.targetId
    - name: Targets.member.1.Port
      in: query
      value: $inputs.port
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      registered: $statusCode
  - stepId: describeTargetHealth
    description: Read back the health of the registered target.
    operationId: describeTargetHealth
    parameters:
    - name: TargetGroupArn
      in: query
      value: $steps.createTargetGroup.outputs.targetGroupArn
    - name: Targets.member.1.Id
      in: query
      value: $inputs.targetId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      healthState: $response.body#/targetHealthDescriptions/0/targetHealth/state
  outputs:
    targetGroupArn: $steps.createTargetGroup.outputs.targetGroupArn
    healthState: $steps.describeTargetHealth.outputs.healthState

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-register-targets-and-check-health-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.