AWS Direct Connect
Browse all Amazonaws APIsAgent-ready OpenAPI document · curated by JenticCloud InfrastructureNetworkinghmac63 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision and manage AWS Direct Connect connections, virtual interfaces, link aggregation groups, and Direct Connect gateways for hybrid network connectivity.
Use for: Provision a new 10G Direct Connect connection at a location, Create a private virtual interface to a VPC via a Direct Connect gateway, List all Direct Connect connections in this account, Allocate a hosted connection to another AWS account
Not supported: Does not handle physical cross-connect installation, on-premises router configuration, or VPC routing tables - use for Direct Connect control-plane provisioning only.
Jentic publishes the only available OpenAPI specification for AWS Direct Connect, keeping it validated and agent-ready. AWS Direct Connect provides dedicated network links between on-premises networks and AWS, bypassing the public internet for lower latency and predictable throughput. The API covers the lifecycle of physical connections, link aggregation groups (LAGs), virtual interfaces (private, public, transit), Direct Connect gateways, and BGP/MACsec configuration. Use it when an agent needs to provision hybrid networking, accept hosted connections, or manage virtual interface attachments to VPCs and Transit Gateways.
Install Jentic One Beta
Connect the AWS Direct Connect to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Direct Connect, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Faws-direct-connect" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Faws-direct-connect" | 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.
Capabilities
What an agent can do with AWS Direct Connect API.
Provision physical connections at Direct Connect locations and bundle them into LAGs for redundancy
Create private, public, and transit virtual interfaces with CreatePrivateVirtualInterface, CreatePublicVirtualInterface, and CreateTransitVirtualInterface
Associate virtual interfaces with VPCs through Direct Connect gateways and gateway associations
Allocate hosted connections and virtual interfaces to other AWS accounts using Allocate operations
Configure BGP peering and MACsec encryption keys on existing connections
Inspect connectivity health via DescribeConnections, DescribeVirtualInterfaces, and DescribeLoa
Use Cases
Patterns agents use AWS Direct Connect API for, with concrete tasks.
★ Stand Up a Hybrid Network Link
Provision a dedicated Direct Connect connection at a colocation facility, request the Letter of Authorisation, and once the cross-connect is in place, attach a private virtual interface to a Direct Connect gateway that fronts the production VPC. The result is a private, predictable link from on-premises to AWS without traversing the public internet.
Call CreateConnection with the location code and 10Gbps bandwidth, then DescribeLoa to retrieve the LOA, and CreatePrivateVirtualInterface once the connection is up.
Multi-Account Hosted Connections
Direct Connect partners and large organisations allocate hosted connections to downstream AWS accounts so each team gets a slice of dedicated bandwidth. AllocateHostedConnection from the partner side and ConfirmConnection from the receiving account complete the handover, keeping ownership and billing aligned per workload.
Call AllocateHostedConnection with the OwnerAccount, Bandwidth, and Vlan parameters, and verify the receiving account confirms via ConfirmConnection.
Connect a Direct Connect Gateway to Transit Gateway
Use Direct Connect gateways and transit virtual interfaces to attach an on-premises network to a Transit Gateway so multiple VPCs across regions share the same physical link. CreateDirectConnectGateway and CreateTransitVirtualInterface establish the path, and AssociateTransitGatewayVirtualInterface connects it to the Transit Gateway.
Call CreateDirectConnectGateway, then CreateTransitVirtualInterface bound to that gateway, and finally CreateDirectConnectGatewayAssociation against the Transit Gateway ID.
Agent-Driven Hybrid Network Operations
An AI agent connected via Jentic can automate Direct Connect operational tasks - accepting partner allocations, rotating MACsec keys, or rebalancing virtual interfaces between LAGs - without bespoke AWS SDK code. Jentic returns the matching Direct Connect operation and schema so the agent can sequence calls correctly across confirmation states.
Search Jentic for 'create a private virtual interface', load the CreatePrivateVirtualInterface schema, and execute it with the connectionId, vlan, asn, and amazonAddress parameters.
Key Endpoints
63 endpoints — jentic publishes the only available openapi specification for aws direct connect, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/#X-Amz-Target=OvertureService.AllocateHostedConnection
Allocate a hosted connection to another account
POST
/#X-Amz-Target=OvertureService.AllocatePrivateVirtualInterface
Allocate a private virtual interface
POST
/#X-Amz-Target=OvertureService.AllocateTransitVirtualInterface
Allocate a transit virtual interface
POST
/#X-Amz-Target=OvertureService.AssociateConnectionWithLag
Associate a connection with a LAG
POST
/#X-Amz-Target=OvertureService.ConfirmConnection
Confirm an allocated connection
POST
/#X-Amz-Target=OvertureService.AssociateMacSecKey
Associate a MACsec key with a connection
POST
/#X-Amz-Target=OvertureService.AcceptDirectConnectGatewayAssociationProposal
Accept a Direct Connect gateway association proposal
POST
/#X-Amz-Target=OvertureService.AllocateHostedConnection
Allocate a hosted connection to another account
POST
/#X-Amz-Target=OvertureService.AllocatePrivateVirtualInterface
Allocate a private virtual interface
POST
/#X-Amz-Target=OvertureService.AllocateTransitVirtualInterface
Allocate a transit virtual interface
POST
/#X-Amz-Target=OvertureService.AssociateConnectionWithLag
Associate a connection with a LAG
POST
/#X-Amz-Target=OvertureService.ConfirmConnection
Confirm an allocated connection
POST
/#X-Amz-Target=OvertureService.AssociateMacSecKey
Associate a MACsec key with a connection
POST
/#X-Amz-Target=OvertureService.AcceptDirectConnectGatewayAssociationProposal
Accept a Direct Connect gateway association proposal
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring AWS Direct Connect by hand means building SigV4 request signing, resolving the regional directconnect.{region}.amazonaws.com host, and handling the X-Amz-Target action dispatch plus AWS retries yourself. Through Jentic you install once, import Direct Connect from the API Directory, store the AWS access keys once, and your agent calls it.
Permission scoping
Direct Connect dispatches every action through a single endpoint with the operation named in the request, so scope the agent to the operations it needs, such as allocating a hosted connection or creating a private virtual interface. Destructive operations like deleting a connection or interface stay out of that set unless you add them.
Credential isolation
Your AWS access keys for Direct Connect are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a private virtual interface' or 'allocate a hosted connection', and Jentic returns the matching Direct Connect operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Direct Connect API through Jentic.
Why is there no official OpenAPI spec for AWS Direct Connect?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Direct Connect via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the AWS Direct Connect API use?
Direct Connect uses AWS Signature Version 4 (HMAC) signing with an AWS access key ID and secret access key. Through Jentic, those credentials live encrypted in your Jentic One instance and are injected into signed requests at execution time, so the agent never sees the raw secret access key.
Can I create a transit virtual interface through this API?
Yes. Use CreateTransitVirtualInterface (or AllocateTransitVirtualInterface for cross-account allocation) with the connectionId, vlan, asn, and the Direct Connect gateway it should attach to. The transit VIF can then be associated with a Transit Gateway via CreateDirectConnectGatewayAssociation.
What are the rate limits for the AWS Direct Connect API?
Direct Connect shares standard AWS service quotas, which are managed per account and region rather than published as fixed per-second limits in the spec. Provisioning operations are infrequent in practice, and ThrottlingException responses should trigger backoff.
How do I provision a private virtual interface through Jentic?
Search Jentic for 'create a private virtual interface', load the CreatePrivateVirtualInterface schema, then execute it with connectionId, vlan, asn, virtualGatewayId or directConnectGatewayId, and customerAddress. Run pip install jentic to use the async SDK pattern.
Does this API carry data traffic, or only manage configuration?
Only manages configuration. Actual customer traffic flows over the physical Direct Connect link and the configured virtual interfaces. The API itself is the control plane for provisioning, allocating, and associating those resources.
Can I limit what my agent is allowed to do with the AWS Direct Connect API?
Yes. Because you run Jentic One yourself, your own rules decide which Direct Connect operations the agent may call and which AWS credentials it can use. Direct Connect dispatches every action through a single endpoint with the operation named in the request, so you scope the agent to only the operations it needs, such as AllocateHostedConnection or CreatePrivateVirtualInterface. Destructive operations like deleting a connection or virtual interface stay outside that set unless you explicitly add them.
GET STARTED