Staticbot logoStaticbot.dev

    Connect your domain at AWS Route 53

    Add the certificate and website records in a Route 53 hosted zone, with an Alias record to CloudFront for your root domain.

    Provider steps checked November 18, 2026. Provider dashboards change; if a button has moved, the official help links at the bottom have the current wording.

    You’ll add two or three records in your AWS Route 53 account: one that proves you own the domain, and the ones that point it at your site. It takes about 10 minutes, it can be undone, and it doesn’t touch your email.

    Your Staticbot deployment page shows the exact values to paste, with a copy button next to each, and checks whether AWS Route 53 is already answering with them. Keep it open next to this guide.

    Before you start

    • If a record already exists for the same name and type, edit it instead of creating a second one.

    Open the DNS records at AWS Route 53

    1. Open the Route 53 console and choose Hosted zones.
    2. Choose your domain’s hosted zone.
    3. Choose Create record.

    Record name and Value are AWS Route 53’s names for the two boxes you fill in. Type only the part before your domain; the console shows the zone name after the box. For the domain itself, leave Record name empty.

    Server-rendered app hosted on Cloudflare? Its deployment page lists TXT records and a CNAME on www pointing at apps.staticbot.app instead of the records below. Add them in the same form, with the same Record name rule.

    Step 1: Add the certificate record

    This record lets Amazon issue the HTTPS certificate for your domain. It doesn’t change where your site or email points. Add one record per certificate record shown on the deployment page:

    TypeCNAME
    Record namethe part before your domain, e.g. _599c0e75…
    Valuethe value ending in .acm-validations.aws
    TTLleave the default

    Save, then go back to the deployment page and click Check my records. Staticbot asks AWS Route 53’s own servers, so you see the answer within seconds. Once it shows Found, the certificate is usually issued within a few minutes.

    Step 2: Point your domain at your site

    The deployment page shows these records once the certificate is issued. If your site lives on a subdomain such as app.yourdomain.com, you only add one CNAME for it.

    For yourdomain.com (the domain itself):

    TypeA record with Alias switched on → Route traffic to “Alias to CloudFront distribution” → paste the address Staticbot shows
    Record nameleave Record name empty
    Valuethe CloudFront address from the deployment page (ends in .cloudfront.net)

    For www.yourdomain.com:

    TypeCNAME
    Record namewww
    Valuethe same CloudFront address
    • If this hosted zone is in the AWS account Staticbot deploys into, Staticbot adds the records itself and the deployment page says “No action needed”.

    Check it worked

    The deployment page checks each record and tells you what it sees: Found, Not found yet, Wrong value, or Domain typed twice (the domain was typed into the Record name box). Most records show up within a minute. Your browser may keep showing the old page for a while after that; a private window shows the new one sooner.

    Working with an AI agent connected to Staticbot? Ask it whether your DNS records are live; it runs the same check.

    Advanced: change nameservers instead

    Instead of adding records, you can point the domain’s nameservers at Staticbot. You then add no records at all: the certificate and the site, the domain itself included, are set up automatically.

    It’s the right choice when you don’t use the domain for anything else yet: no email on it, no other subdomains. The deployment page recommends it in that case. If the domain has email, Staticbot copies the email records it can see on the domain itself before you switch; records on other names (such as blog.yourdomain.com or email signing keys) have to be re-created, so adding records is usually the safer route there. The deployment page only offers the switch when it’s safe to.

    At AWS Route 53:

    If the domain is registered through Route 53: Registered domains → select the domain → Actions → Edit name servers. Replace them with the Staticbot nameservers and update. This is the registrar setting, not a hosted zone’s NS record. Turn off DNSSEC signing first if it is on.

    More about what moves and what to check: changing nameservers.

    AWS Route 53’s own help pages

    ← All DNS providers