Elastic Load Balancing

Name: Elastic Load Balancing API
Brand: Elastic Load Balancing
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingapiKey68 EndpointsREST

For Agents

Create Application, Network, and Gateway Load Balancers, manage listeners and routing rules, and register targets across AWS regions through a single API.

Connect the Elastic Load Balancing to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Elastic Load Balancing, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Elastic Load Balancing API.

Create Application, Network, and Gateway Load Balancers across multiple Availability Zones

Define listeners and listener rules with path, host, header, and source IP conditions

Configure target group health checks, deregistration delay, and stickiness attributes

GET STARTED

Start building with Elastic Load Balancing API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Elastic Load Balancing, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Elastic Load Balancing, keeping it validated and agent-ready. Elastic Load Balancing v2 covers Application, Network, and Gateway Load Balancers on AWS. The API manages load balancer creation, listeners, routing rules, target groups, target registration, and health checks across multiple Availability Zones. It is built for platform and SRE teams that need to programmatically expose services, shift traffic between target groups, and roll out blue-green or weighted deployments without console interaction.

Use Cases

Patterns agents use Elastic Load Balancing API for, with concrete tasks.

★ Application Load Balancer Provisioning

Platform teams use the Elastic Load Balancing API to provision Application Load Balancers in front of containerised services and EC2 fleets. The API drives load balancer creation, listener setup, target group registration, and health-check configuration so that infrastructure pipelines can stand up internet-facing or internal endpoints without console steps. A standard ALB with two listeners and three target groups can be provisioned in under five minutes when run as an automated workflow.

Create an internet-facing Application Load Balancer in subnets subnet-a and subnet-b, then attach an HTTPS listener forwarding to target group api-prod.

Blue-Green and Canary Traffic Shifting

Deployment systems use ELBv2 listener rules with weighted target groups to shift traffic between blue and green stacks during release. The API lets a release controller adjust forward action weights from 100/0 to 90/10 to 50/50 in seconds, with rollback by reversing the same call. Health-check signals on each target group gate the next traffic step.

Modify the listener rule on listener arn:...:listener/app/prod/abc to forward 90 percent to target group blue and 10 percent to target group green.

Target Health Monitoring

Reliability teams use the API to read target health states across hundreds of target groups in response to incidents and scaling events. The DescribeTargetHealth call returns per-target state, reason codes, and descriptions so that runbooks can pinpoint failing instances before paging humans. The same API powers automated remediation that deregisters chronically unhealthy targets and triggers replacement via Auto Scaling.

List all targets in target group prod-api with state unhealthy and return the reason code and description for each.

Agent-Driven Load Balancer Operations via Jentic

AI agents use the ELBv2 API through Jentic to perform routine traffic operations such as registering new targets after a deploy, updating listener rules, and rotating TLS certificates. Jentic exposes ELBv2 operations as discoverable tools so an agent can search by intent and execute the matching call without parsing AWS docs. This compresses release-time traffic management from manual console work to a single agent action.

Search Jentic for register target with load balancer, load the RegisterTargets schema, and execute it for instance i-0123456789abcdef0 in target group api-prod.

Key Endpoints

68 endpoints — jentic publishes the only available openapi specification for elastic load balancing, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#Action=CreateLoadBalancer

Create a load balancer

POST

/#Action=CreateListener

Create a listener on a load balancer

POST

/#Action=CreateTargetGroup

Create a target group

POST

/#Action=CreateRule

Create a listener rule

POST

/#Action=DeleteLoadBalancer

Delete a load balancer

POST

/#Action=AddListenerCertificates

Add TLS certificates to a listener

POST

/#Action=AddTags

Tag load balancers and target groups

POST

/#Action=CreateLoadBalancer

Create a load balancer

POST

/#Action=CreateListener

Create a listener on a load balancer

POST

/#Action=CreateTargetGroup

Create a target group

POST

/#Action=CreateRule

Create a listener rule

POST

/#Action=DeleteLoadBalancer

Delete a load balancer

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys for ELBv2 are stored encrypted in the Jentic vault. Agents receive scoped, short-lived signing access — raw secret access keys never enter the agent context.

Intent-based discovery

Agents search by intent (for example create a load balancer) and Jentic returns matching ELBv2 operations with their input schemas, so the agent can call the right action without browsing AWS docs.

Time to first call

Direct ELBv2 integration: 1-2 days for SigV4 signing, query-protocol handling, and pagination. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amazon EC2

EC2 provides the instances that ELBv2 registers as targets

Choose EC2 when you need to launch, describe, or terminate the instances that sit behind a load balancer.

Complementary

Amazon EKS

Runs Kubernetes services that are typically exposed via ALB or NLB

Choose EKS when the workload behind the load balancer is a Kubernetes service managed by AWS Load Balancer Controller.

Complementary

Amazon Route 53

Maps human-readable DNS names to ELBv2 load balancer endpoints

Choose Route 53 when you need to point a custom domain at a load balancer DNS name with alias records.

FAQs

Specific to using Elastic Load Balancing API through Jentic.

Why is there no official OpenAPI spec for Elastic Load Balancing?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Elastic Load Balancing via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Elastic Load Balancing API use?

ELBv2 uses AWS Signature Version 4 request signing. Through Jentic, AWS access keys are stored encrypted in the vault and signing happens server-side, so the raw secret access key never reaches the agent.

Can I shift traffic between target groups with this API?

Yes. ModifyListener and ModifyRule accept a forward action with multiple TargetGroups and per-group Weight values. Adjusting weights live lets you implement blue-green and canary patterns without recreating the listener.

What are the rate limits for the Elastic Load Balancing API?

AWS applies per-account, per-region throttling. Mutating calls such as CreateLoadBalancer and CreateRule are throttled more aggressively than Describe calls. Use exponential backoff on ThrottlingException responses; AWS does not publish exact TPS numbers in the spec.

How do I register a target with a target group through Jentic?

Search Jentic for register targets, load the schema for the RegisterTargets action, and execute it with the TargetGroupArn and a Targets array containing instance IDs or IP addresses. Jentic returns the call result once registration completes.

Does the ELBv2 API manage Classic Load Balancers?

No. This v2 API covers Application, Network, and Gateway Load Balancers. Classic Load Balancers use the older elasticloadbalancing v1 API, which is a separate service with different action names.