For Agents
Provision and manage AWS Global Accelerator resources to route user traffic across AWS regions through static anycast IPs, with full control over listeners, endpoint groups, and traffic dials.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Global Accelerator, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 instanceJentic 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.
What an agent can do with AWS Global Accelerator API.
Create standard and custom routing accelerators with static anycast IP addresses
Configure listeners on TCP and UDP ports and attach endpoint groups across regions
Add and remove EC2, ALB, NLB, or EIP endpoints from endpoint groups
Advertise customer-owned IP CIDR ranges (BYOIP) onto the AWS edge network
GET STARTED
Use for: I need to create a Global Accelerator with two static anycast IP addresses, Set up a TCP listener on port 443 routing traffic to an Application Load Balancer in us-east-1, Add a new endpoint group in eu-west-1 with a 50% traffic dial, List all accelerators in my account and their status
Not supported: Does not handle DNS resolution, regional load balancing, or compute provisioning — use for anycast traffic acceleration and global endpoint routing only.
Jentic publishes the only available OpenAPI document for AWS Global Accelerator, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for AWS Global Accelerator, keeping it validated and agent-ready. AWS Global Accelerator is a networking service that improves the availability and performance of applications by routing user traffic through the AWS global network to optimal regional endpoints. It provisions static anycast IP addresses, configures listeners and endpoint groups, and supports both standard and custom routing accelerators. The API covers full lifecycle management of accelerators, listeners, endpoint groups, BYOIP CIDR advertisement, and cross-account attachments across 49 endpoints.
Allow or deny custom routing traffic to specific destination addresses and ports
Manage cross-account attachments to share endpoint resources between AWS accounts
Tag accelerators and update traffic dials to shift traffic between regions
Patterns agents use AWS Global Accelerator API for, with concrete tasks.
★ Multi-Region Application Failover
Front a multi-region application with two static anycast IP addresses so clients reach the closest healthy regional endpoint. Global Accelerator continuously health-checks endpoint groups and shifts traffic within seconds when a region degrades, removing the need for DNS-based failover that depends on resolver TTLs. Setup takes under an hour for a two-region deployment with existing ALBs.
Create a standard accelerator named prod-frontend, add a TCP listener on port 443, and create endpoint groups in us-east-1 and eu-west-1 each pointing at an existing ALB ARN with a 100 traffic dial
Custom Routing for Multi-Tenant VPC Workloads
Use a custom routing accelerator to map deterministic destination IPs and ports onto specific subnets and EC2 instances inside customer VPCs. This is the primary pattern for real-time gaming, voice, and multi-tenant SaaS where each session must hit a specific compute target. The API exposes AddCustomRoutingEndpoints, AllowCustomRoutingTraffic, and DenyCustomRoutingTraffic for fine-grained mapping control.
Create a custom routing accelerator, add a port range listener for 5000-6000 UDP, attach endpoint groups for two VPC subnets, and call AllowCustomRoutingTraffic to permit traffic to a specific destination address
BYOIP Migration to AWS Edge
Bring an organisation's owned IPv4 CIDR onto Global Accelerator so customers continue to hit the same IP ranges they have whitelisted while traffic is now served through the AWS global edge network. ProvisionByoipCidr, AdvertiseByoipCidr, and WithdrawByoipCidr let an agent move blocks in and out of advertisement programmatically.
Provision the BYOIP CIDR 203.0.113.0/24 with a signed authorisation message, then call AdvertiseByoipCidr once the CIDR is in PROVISIONED state
AI Agent Traffic Operations
Through Jentic, an AI agent can operate Global Accelerator as a runtime traffic-shaping tool — adjusting endpoint weights, traffic dials, and listener health checks in response to incident alerts or capacity signals. Jentic exposes the operations as discoverable tools so the agent can search by intent and execute the right call without browsing the AWS docs.
Search Jentic for 'shift traffic between aws regions', load the UpdateEndpointGroup schema, and execute it to set endpoint group us-west-2 traffic dial to 0 during an incident
49 endpoints — jentic publishes the only available openapi specification for aws global accelerator, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/
CreateAccelerator — provision a new standard accelerator
/
CreateCustomRoutingAccelerator — provision a custom routing accelerator
/
CreateListener — add a listener on an accelerator
/
CreateEndpointGroup — add a regional endpoint group
/
AddEndpoints — attach endpoints to an endpoint group
/
AdvertiseByoipCidr — advertise a customer-owned CIDR
/
UpdateAccelerator — change name, IP type, or enabled state
/
ListAccelerators — list all accelerators in the account
/
CreateAccelerator — provision a new standard accelerator
/
CreateCustomRoutingAccelerator — provision a custom routing accelerator
/
CreateListener — add a listener on an accelerator
/
CreateEndpointGroup — add a regional endpoint group
/
AddEndpoints — attach endpoints to an endpoint group
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys for Global Accelerator are stored encrypted in the Jentic vault. Agents never see the raw credentials — Jentic signs each request with SigV4 server-side and returns the response.
Intent-based discovery
Agents search Jentic with intents like 'create an aws global accelerator' or 'shift traffic between regions' and get back the matching operation with its input schema, ready to execute.
Time to first call
Direct integration: 1-2 days to wire up the AWS SDK, IAM roles, and SigV4 signing. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Amazon Route 53
DNS-based traffic routing for multi-region failover, an alternative to anycast routing
Choose Route 53 when DNS-level failover and geolocation routing are sufficient and you do not need static anycast IPs or sub-second failover.
AWS Elastic Load Balancing v2
ALB and NLB endpoints that sit behind Global Accelerator endpoint groups
Use ELBv2 to manage the regional load balancers themselves; use Global Accelerator to front them with anycast IPs.
Amazon EC2
EC2 and Elastic IP resources that can be attached as Global Accelerator endpoints
Use EC2 to provision and manage compute and Elastic IPs that are then registered as endpoints in Global Accelerator endpoint groups.
Specific to using AWS Global Accelerator API through Jentic.
Why is there no official OpenAPI spec for AWS Global Accelerator?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Global Accelerator 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 AWS Global Accelerator API use?
The API uses AWS Signature Version 4 (HMAC) request signing with an AWS access key ID and secret access key. Through Jentic, the AWS credentials are stored encrypted in the vault and the agent receives scoped, signed requests rather than raw secrets.
Can I create a multi-region accelerator with the AWS Global Accelerator API?
Yes. Call CreateAccelerator to provision the accelerator and its static IPs, CreateListener to define the port and protocol, then CreateEndpointGroup once per region with the matching EndpointGroupRegion field. Each endpoint group can hold ALBs, NLBs, EC2 instances, or Elastic IPs from that region.
What are the rate limits for the AWS Global Accelerator API?
AWS applies per-account, per-region request quotas to Global Accelerator API calls and these vary by operation. List and describe operations are higher-throughput than create and update operations. Check the AWS Service Quotas console for current limits and request increases there.
How do I shift traffic between regions through Jentic?
Search Jentic for 'update endpoint group traffic dial', load the UpdateEndpointGroup schema, and execute with the EndpointGroupArn and a new TrafficDialPercentage value. A dial of 0 stops new connections to that region; existing connections continue until they close.
Can I use my own IP ranges with AWS Global Accelerator?
Yes. Call ProvisionByoipCidr with a signed RFC 2622 authorisation message to register a /24 or larger IPv4 block, then AdvertiseByoipCidr once the block reaches PROVISIONED state. Use WithdrawByoipCidr and DeprovisionByoipCidr to reverse the process.
/
AdvertiseByoipCidr — advertise a customer-owned CIDR
/
UpdateAccelerator — change name, IP type, or enabled state
/
ListAccelerators — list all accelerators in the account