Amazon Route 53 Integration Coming Q1 2025

Prerequisites

• An AWS account with Route 53 hosted zones
• IAM user or role with the following permissions:
  • route53:ListHostedZones
  • route53:GetHostedZone
  • route53:ListResourceRecordSets

Creating IAM Credentials

1. Log in to AWS Console

   Visit the AWS IAM Console and log in to your account.

2. Create a new IAM User

   Create a new IAM user specifically for DNS Check integration:

   • Choose "Programmatic access" for access type
   • Note: This will provide an Access Key ID and Secret Access Key
   
3. Attach Required Permissions

   Create a custom policy with the following JSON:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Effect": "Allow",
               "Action": [
                   "route53:ListHostedZones",
                   "route53:GetHostedZone",
                   "route53:ListResourceRecordSets"
               ],
               "Resource": "*"
           }
       ]
   }

   
4. Save Credentials

   After creating the user, you'll be shown the Access Key ID and Secret Access Key. Make sure to save these somewhere safe - you won't be able to see the Secret Access Key again!

Connecting to DNS Check

1. Add Route 53 integration

   In DNS Check, go to Settings > Integrations and click "Add Route 53".

2. Enter AWS credentials

   Enter your Access Key ID and Secret Access Key.

3. Select hosted zones

   Choose which hosted zones you want to monitor. DNS Check will automatically detect all available zones in your account.

Monitoring DNS Records

Once connected, DNS Check will:

• Automatically detect all DNS records in your selected hosted zones
• Monitor for any changes to these records
• Alert you when changes are detected
• Keep a history of all changes for future reference

Troubleshooting

Common Issues

• "Unable to list hosted zones"

  This usually means the IAM user doesn't have the correct ListHostedZones permission. Review the IAM policy attached to your user.

• "Unable to fetch DNS records"

  Verify that the IAM user has ListResourceRecordSets permission for the hosted zones you're trying to monitor.

• "Invalid credentials"

  Double-check that you've entered the correct Access Key ID and Secret Access Key.