One place for your Route 53 DNS, domains and ACM certificates
See DNS changes, domain renewals and certificate expiry before they become problems
Connect your AWS account and InfraNest takes over tracking and managing Route 53 DNS, Route 53 domains and ACM certificates.
- DNS zones are found automatically — existing Route 53 zones are imported on connect, no manual re-entry.
- Records can be managed from InfraNest — create, edit and delete A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, CAA, PTR, NAPTR and DS records, and the change is written back to AWS.
- Domains stay tracked — expiry dates, nameservers and lock state sync automatically, and you can register, transfer, renew, manage contacts, DNSSEC, WHOIS privacy and auto-renew from InfraNest.
- Certificates are watched for you — ACM certificates and their expiry show up alongside everything else, with alerts you can wire into an automation when a certificate is about to expire, revoked or changes unexpectedly.
- More than one AWS account can be connected — manage DNS, domains and certificates across accounts without switching logins.
What it looks like in InfraNest
What you can do
Once Amazon AWS is connected, this is what InfraNest can do with it.
- Zones imported automatically on connect
- DNS records editable and pushed back to AWS
- Domain and certificate expiry tracked automatically
- Multiple AWS accounts in one view
- Spend on DNS, domains and certificates totalled in one place
Not supported
InfraNest doesn't manage AWS cloud servers (EC2) through this integration — DNS, domain registration and certificates are covered, but server infrastructure isn't.
How to connect it
- 1
Open the AWS integration
Start the connection from Integrations → AWS.
- 2
Choose what to manage
Pick DNS (Route 53), Domains (Route 53) and/or Certificates (ACM) depending on what you want InfraNest to track.
- 3
Add your credentials and regions
Enter your role ARN or access keys, then select the regions you use — ACM certificates live in a specific region, so pick the ones that matter.
- 4
Connect
Select Connect and InfraNest imports your existing zones, domains and certificates automatically.
That’s it — Amazon AWS is connected.
Full setup guideSet up with AI
I use Amazon AWS, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: IAM role or access keys. Walk me through creating that in Amazon AWS: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.
What syncs
What InfraNest keeps in sync with Amazon AWS.
| DNS zones | DNS zones and records |
| Domains | Domains, expiry dates, nameservers and lock state |
| Certificates | Certificates and their expiry |
MCP server
Amazon AWS in Claude and ChatGPT
Connect your AI assistant to InfraNest and ask about your Amazon AWS account in plain words, next to every other provider you use. It reads, and acts only when you allow it.
- Which of my Amazon AWS domains expire in the next 60 days?
- Where does shop.example.com point, and did anything change there this week?
- Which certificates expire this month, and does anything renew them?
Questions
#Will this manage my EC2 servers too?
No — this integration covers Route 53 DNS, Route 53 domain registration and ACM certificates only. Cloud server management isn't supported through AWS yet.
#Can I connect more than one AWS account?
Yes, you can connect multiple AWS accounts and manage DNS, domains and certificates across all of them from the same place.
#Can InfraNest change things in my AWS account, or just read them?
With DNS enabled, InfraNest can create, edit and delete Route 53 records and zones, and those changes are sent to AWS. Domain actions like renewals, transfers and nameserver changes work the same way — nothing changes on the AWS side unless you do it through InfraNest.
#What happens if my AWS credentials are revoked or expire?
InfraNest will flag the connection as failing and pause the affected features until you update the credentials. Nothing is deleted on either side while the connection is down — you just won't see new changes until it's reconnected.
#What do I need before connecting Amazon Web Services?
You need an AWS IAM role or access keys with read-only access (ReadOnlyAccess is enough) — see the setup guide.
#Is there a Amazon AWS MCP server?
Yes, through InfraNest. Once Amazon AWS is connected, InfraNest’s MCP server lets Claude, ChatGPT, Cursor, VS Code and other assistants read your domains, DNS records and certificates at Amazon AWS, together with every other provider you use. It works on every plan, including Free. Amazon AWS also runs its own MCP server for your Amazon AWS account alone. InfraNest’s answers across all your providers, with your monitors and incidents in the same answer.
One dashboard for every provider
Add this integration, then the rest of your stack — domains, DNS, servers, certificates and monitoring in one place.
Free plan · No credit card required · Set up in minutes