Skip to main content

AWS Route 53

AWS Route 53 integration allows your product to fetch DNS records, hosted zones, and domain configurations. This is useful for inventory, monitoring, and validating domain setups.

Credentials Needed​

Required credentials:

  • Access Key ID
  • Secret Access Key

You can use an IAM user or an IAM role if the integration runs from within AWS (EC2, Lambda, ECS).

IAM Permissions​

To read Route 53 hosted zones and DNS records, the following read-only permissions are required:

Service Actions:

  • Route 53: route53:ListHostedZones, route53:ListResourceRecordSets

IAM Policy JSON​

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

Creating Users​

  1. Go to AWS Console → IAM → Users → Add User
  2. Name the user (e.g., Route53IntegrationUser)
  3. Select Programmatic Access
  4. Attach the Route53ReadOnly policy created above
  5. Finish creation and copy the Access Key ID and Secret Access Key

Optionally, if running integration inside AWS, attach this policy to an IAM Role.

Test Connectivity​

Use AWS CLI or SDK to verify read-only access:

# List hosted zones
aws route53 list-hosted-zones --region us-east-1 --access-key <ACCESS_KEY> --secret-key <SECRET_KEY>

# List DNS records for a hosted zone
aws route53 list-resource-record-sets --hosted-zone-id <HOSTED_ZONE_ID>

Ensure you can fetch hosted zone details and resource record sets successfully.

Save the Results in the Platform and Create Connection​

  1. Store credentials securely in your platform:
    • AWS_ACCESS_KEY_ID
    • AWS_SECRET_ACCESS_KEY
    • AWS_REGION
  2. Create a connection configuration in your product pointing to AWS Route 53
  3. Validate the connection by fetching hosted zones and DNS records

Best Practices​

  • Use least privilege principle—read-only access only
  • Prefer IAM Roles over static keys when running integration in AWS
  • Limit access to specific regions if only required
  • Rotate credentials periodically
  • Encrypt secrets in your platform and avoid hardcoding