Manage Amazon AWS from InfraNest
See every Route 53 domain, zone and ACM certificate in one place
Connect an AWS account and InfraNest brings your Route 53 DNS, domains and ACM certificates into one view.
- DNS zones are found automatically — existing Route 53 hosted zones are imported on connect, no manual re-entry.
- Records stay in sync both ways — edit a record in InfraNest or in AWS and the change is reflected correctly on the other side.
- Domain expiry and lock state are tracked for you — nameservers, auto-renew, transfer lock, DNSSEC and WHOIS privacy are visible without opening Route 53.
- Certificate expiry is watched automatically — ACM certificates appear in your certificate list so you can see what's expiring before it becomes an outage.
- More than one AWS account can be connected at once — manage several accounts side by side instead of switching between them.
NoteDNS zones you host in Route 53 don't need to be registered there — any domain, wherever it's registered, can point to a Route 53 zone.
What you can do
- Automatic zone discovery on connect
- Two-way DNS record sync
- Domain expiry, lock and nameserver tracking
- ACM certificate expiry tracking
- Multiple AWS accounts at once
Not supported
InfraNest doesn't manage AWS cloud servers (EC2) through this integration — DNS, domains and certificates are covered, but EC2 instances aren't yet. Use the AWS console for that until support is added.
How to connect it
- 1
Create read-only access in AWS
Set up an IAM role (recommended) or IAM user with the ReadOnlyAccess scope. An assumed role avoids storing long-lived keys.
- 2
Open the AWS integration
Go to Integrations and open AWS. Optionally give the connection an Account label to tell multiple connections apart.
- 3
Choose what to manage
Pick DNS (Route 53), Domains (Route 53), Certificates (ACM), or any combination, then enter your role ARN or access keys.
- 4
Pick your regions and connect
Select the regions your ACM certificates live in — Route 53 itself is global — then select Connect.
What syncs
| DNS zones | DNS zones and records |
| Domains | Domains, expiry dates, nameservers and lock state |
| Certificates | Certificates and their expiry |
Questions
#What AWS permissions does InfraNest need?
A ReadOnlyAccess scope is all InfraNest needs to read your Route 53 zones, domains and ACM certificates. Editing DNS records requires the same connection but the read-only scope covers everything InfraNest displays.
#What happens if I revoke the role or delete the access keys?
InfraNest can no longer read or update your AWS resources, and syncing stops. Nothing already imported is deleted — you'll see a connection error until you reconnect with valid access.
#Can InfraNest make changes in my AWS account, or is it read-only?
With DNS enabled, InfraNest can create, edit and delete Route 53 records and zones, and those changes are sent to AWS. Domain settings like nameservers, auto-renew, transfer lock and WHOIS privacy can also be changed from InfraNest.
#Why is a certificate missing from my list?
ACM certificates live in a specific region, so check that the region the certificate is in is selected on the connection. Add that region and reconnect if needed.
#Can I connect more than one AWS account?
Yes, InfraNest supports connecting multiple AWS accounts at once, and each shows up as a separate connection labelled by name so you can tell them apart.
Start in seconds
Bring your whole infrastructure into one modern dashboard.
Free plan · No credit card required · Set up in minutes