AWS Amazon Route 53
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkinghmac70 EndpointsREST
For Agents
Manage DNS records, hosted zones, health checks, and domain registrations on AWS's authoritative DNS, with weighted, latency, and geolocation routing.
Use for: I need to create an A record pointing api.example.com at a load balancer, List all DNS record sets in a Route 53 hosted zone, Create a new hosted zone for example.com, Set up a health check for the production API endpoint
Not supported: Does not handle email delivery, web application firewalling, or VPC routing — use for authoritative DNS, hosted zones, health checks, and DNS-based traffic routing only.
Jentic publishes the only available OpenAPI specification for Amazon Route 53, keeping it validated and agent-ready. Amazon Route 53 is AWS's authoritative DNS, domain registration, and traffic-routing service. It manages public and private hosted zones, lets you create DNS records with health checks and failover policies, supports advanced traffic routing (weighted, latency-based, geolocation, geoproximity), and offers DNSSEC signing for zones. The same API also handles domain registration and CIDR-based traffic routing.
Install Jentic One Beta
Connect the Amazon Route 53 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Route 53, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: 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 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 Amazon Route 53 API.
Create and manage public and private hosted zones for authoritative DNS
Apply batch record-set changes with ChangeResourceRecordSets including CREATE, UPSERT, and DELETE actions
Configure DNS health checks and failover policies tied to record sets
Apply traffic routing policies including weighted, latency-based, geolocation, and geoproximity
Manage CIDR collections and CIDR-locations for IP-block-based DNS routing
Enable and manage DNSSEC for hosted zones via key-signing-key activation
Use Cases
Patterns agents use Amazon Route 53 API for, with concrete tasks.
★ Authoritative DNS for production services
Platform teams use Route 53 hosted zones as the authoritative DNS for production traffic, creating A and AAAA alias records that point at load balancers, CloudFront distributions, and API Gateway endpoints. ChangeResourceRecordSets applies record changes atomically and returns a change ID that can be polled until INSYNC, which keeps deployments deterministic.
Submit ChangeResourceRecordSets with an UPSERT action to create an alias A record api.example.com pointing at the prod ALB, then poll GetChange until status is INSYNC.
Multi-region failover and traffic routing
Reliability teams use Route 53 health checks combined with failover routing policies to direct traffic away from unhealthy regions. CreateHealthCheck registers an endpoint to monitor; record sets reference the health check and apply Failover, Weighted, or Latency policies to route around failure. The same primitives enable canary releases by adjusting record weights.
Create a health check on https://prod-eu.example.com/health, then upsert two A records api.example.com with Failover routing — primary in eu-west-1, secondary in us-east-1 — both referencing the health check.
Private DNS for VPC-internal services
Networking teams use private hosted zones to give VPC-internal services memorable names that only resolve inside associated VPCs. CreateHostedZone with a VPC parameter creates the zone; AssociateVPCWithHostedZone extends resolution to additional VPCs. This avoids exposing internal service names to public DNS.
Create a private hosted zone internal.example.com tied to vpc-abc123, then call AssociateVPCWithHostedZone to extend resolution to vpc-def456.
Agent-driven DNS automation through Jentic
AI agents that manage infrastructure-as-code workflows use Jentic to call ChangeResourceRecordSets, GetChange, and CreateHealthCheck without holding raw AWS credentials. Jentic stores the agent's keys in the MAXsystem vault, signs each request with SigV4, and returns the structured response — letting the agent confirm propagation status before declaring the change complete.
Search Jentic for 'create a Route 53 DNS record', load ChangeResourceRecordSets, and execute it with an UPSERT action for a new staging subdomain, then poll GetChange until INSYNC.
Key Endpoints
70 endpoints — jentic publishes the only available openapi specification for amazon route 53, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/2013-04-01/hostedzone
Create a hosted zone
POST
/2013-04-01/hostedzone/{Id}/rrset/
Apply batch record-set changes
POST
/2013-04-01/healthcheck
Create a DNS health check
POST
/2013-04-01/hostedzone/{Id}/associatevpc
Associate a VPC with a private hosted zone
POST
/2013-04-01/keysigningkey/{HostedZoneId}/{Name}/activate
Activate a DNSSEC key-signing key
POST
/2013-04-01/cidrcollection
Create a CIDR collection for IP-block routing
POST
/2013-04-01/tags/{ResourceType}/{ResourceId}
Apply tags to a Route 53 resource
POST
/2013-04-01/hostedzone
Create a hosted zone
POST
/2013-04-01/hostedzone/{Id}/rrset/
Apply batch record-set changes
POST
/2013-04-01/healthcheck
Create a DNS health check
POST
/2013-04-01/hostedzone/{Id}/associatevpc
Associate a VPC with a private hosted zone
POST
/2013-04-01/keysigningkey/{HostedZoneId}/{Name}/activate
Activate a DNSSEC key-signing key
POST
/2013-04-01/cidrcollection
Create a CIDR collection for IP-block routing
POST
/2013-04-01/tags/{ResourceType}/{ResourceId}
Apply tags to a Route 53 resource
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS credentials are stored encrypted in the Jentic vault (MAXsystem). Each Route 53 call is signed with SigV4 server-side; the agent only receives scoped, short-lived authorisation, so raw access keys never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'create a Route 53 DNS record') and Jentic returns matching Route 53 operations with their input schemas, so the agent calls ChangeResourceRecordSets without browsing AWS docs.
Time to first call
Direct Route 53 integration: 1-2 days for SigV4 signing against the global endpoint, ChangeBatch construction, and INSYNC polling. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Amazon Route 53 API through Jentic.
Why is there no official OpenAPI spec for Amazon Route 53?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Route 53 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 Amazon Route 53 API use?
Route 53 uses AWS Signature Version 4 HMAC signing with an access key ID and secret access key, optionally with a session token. The Route 53 control plane is global, so requests are signed against the us-east-1 endpoint. Through Jentic, your credentials sit in the MAXsystem vault and Jentic signs each request server-side.
Can I create alias records to AWS load balancers with Amazon Route 53?
Yes. Use ChangeResourceRecordSets with an UPSERT or CREATE action and an AliasTarget pointing at the ELB DNS name and hosted zone ID. Alias records are zero-cost lookups and resolve directly to the load balancer's IPs without an extra DNS hop.
What are the rate limits for the Amazon Route 53 API?
AWS publishes a default of 5 requests per second per account for most Route 53 operations, with higher limits available on request. ChangeResourceRecordSets accepts up to 1,000 changes per call, but only 32,000 changes per hosted zone per 24 hours. Production agents should batch changes and back off on Throttling errors.
How do I create a DNS record with Amazon Route 53 through Jentic?
Search Jentic for 'create a Route 53 DNS record', load ChangeResourceRecordSets, and call POST /2013-04-01/hostedzone/{Id}/rrset/ with a ChangeBatch containing an UPSERT action and the record details. Then poll GetChange with the returned change ID until status is INSYNC. Install with pip install jentic.
Can Amazon Route 53 register domain names as well as serve DNS?
Yes — Route 53 includes a domain-registration sub-API for registering, transferring, and renewing domains, separate from the DNS-record APIs covered in this spec. Domain registration calls live on the route53domains endpoint; DNS record management lives on the route53 endpoint.
GET STARTED