---
title: "Amazon Route53"
slug: "aws-route-53"
updated: 2025-03-18T20:56:18Z
published: 2025-03-18T20:56:18Z
canonical: "docs.databee.buzz/aws-route-53"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon Route53

Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. Route 53 performs domain registration, DNS routing, and health checking. DNS query logs are not accessible directly through AWS Route53. CloudWatch logs are used to view AWS Route53 DNS query logs in near real-time.

For more information on AWS Route53, click [here](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/Welcome.html).

**Integration Method:** API

**Tables**: DNS Activity (4003)

This integration supports the following events.

| Events | Description |
| --- | --- |
| DNS Query | Information about the public DNS queries that Route 53 receives |

This integration supports the following versions.

| AWS Route53 API version | 20140328 |
| --- | --- |

## Prerequisites

- To configure CloudWatch Log groups for AWS Route53, refer [here](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/query-logs.html#query-logs-configuring).
- Refer to this [common procedure](https://docs.databee.buzz/docs/prerequisites-aws-configuration) on how to create an IAM user, configure the AWS Access Key and AWS Secret Key, attach an IAM policy with required permissions.

## Configuration Overview

1. Configure AWS Route53 to route logs to CloudWatch.
2. Generate an AWS Access Key & Secret Key with the required IAM policies.
3. Add the [AWS Route53 data feed](/user-manual/docs/aws-route-53#databee-configuration) in the DataBee console with the required Access Key and Secret Key.

| **DataBee Parameter** | **AWS Parameters** |
| --- | --- |
| Access Key | AWS Access Key |
| Secret Key | AWS Secret Key |
| AWS Region | AWS Region |
| Service Name | logs |
| Log Group ARN | CloudWatch Log group ARN for AWS Route53 DNS query logs |

## AWS Route53 – IAM Policy Information

1. Start by creating a IAM user with the API credentials. This common step is documented at [AWS Configuration Prerequisites](https://docs.databee.buzz/docs/prerequisites-aws-configuration).
2. Once the IAM user has been created, the following permissions will need to be added to a role associated with the user. Refer to [Adding Permissions to an IAM user](https://docs.databee.buzz/docs/prerequisites-aws-configuration#adding-permissions-to-an-iam-user) for the steps.
3. Ensure AWS Access Key is attached to an IAM policy with following Actions allowed on the CloudWatch log group resource. For reference, you can check the below required minimum IAM policy.

- logs:DescribeLogGroups
- logs:DescribeLogSteams
- logs:GetLogEvents

Required Minimum IAM policy

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "logs:DescribeLogGroups",
        "logs:DescribeLogStreams",
        "logs:GetLogEvents"
      ],
      "Resource": [
        "arn:aws:logs:*:*:*"
      ]
    }
  ]
}
```

## DataBee Configuration

1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-route53-mar2025-image-r2ykdi7l.png?sv=2026-02-06&spr=https&st=2026-11-03T16%3A19%3A52Z&se=2026-11-03T17%3A19%3A52Z&sr=c&sp=r&sig=OuWKmDwstApvWKtYqrRKFqkTWS%2B76nPp4juv%2Fz291fI%3D)
2. Search for the **AWS Route53** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-route53-mar2025-image-igiv5ctp.png?sv=2026-02-06&spr=https&st=2026-11-03T16%3A19%3A52Z&se=2026-11-03T17%3A19%3A52Z&sr=c&sp=r&sig=OuWKmDwstApvWKtYqrRKFqkTWS%2B76nPp4juv%2Fz291fI%3D)
3. Click on the **API Ingest** option for collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-route53-mar2025-image-oy0nzxu9.png?sv=2026-02-06&spr=https&st=2026-11-03T16%3A19%3A52Z&se=2026-11-03T17%3A19%3A52Z&sr=c&sp=r&sig=OuWKmDwstApvWKtYqrRKFqkTWS%2B76nPp4juv%2Fz291fI%3D)
4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-route53-mar2025-image-ytevl5a7.png?sv=2026-02-06&spr=https&st=2026-11-03T16%3A19%3A52Z&se=2026-11-03T17%3A19%3A52Z&sr=c&sp=r&sig=OuWKmDwstApvWKtYqrRKFqkTWS%2B76nPp4juv%2Fz291fI%3D)
5. In the configuration page, confirm the following:
  - API Base URL: this is the base URL that DataBee will interact with. Replace <aws-region> with appropriate AWS region.
  - Authorization Method: AWS Signature
  - Access Key: paste the AWS Client Access Key.
  - Secret Key: paste the AWS Client Secret Key.
  - Session Token: can be left empty.
  - AWS Region: type the AWS region.
  - Service Name: logs
  - Event types: preselected for all the event types that integration pulls.
  - Log Group ARN: paste the CloudWatch log group created for AWS Route53.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-route53-mar2025-image-c865nwf5.png?sv=2026-02-06&spr=https&st=2026-11-03T16%3A19%3A52Z&se=2026-11-03T17%3A19%3A52Z&sr=c&sp=r&sig=OuWKmDwstApvWKtYqrRKFqkTWS%2B76nPp4juv%2Fz291fI%3D)

1. Click **Submit**.

## Troubleshooting Tips

- Ensure the Access Key, Secret Key, Log Group ARN are pasted correctly. Since you cannot view the Secret Key after the 1st time, re-create the AWS Access Key & AWS Secret Key, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed.
- Ensure the AWS Route53 scopes/permissions are correctly attached to the AWS Access Key.