---
title: Getting Started with Datadog
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Infrastructure > Datadog Resource Catalog
---

# aws_route53resolver_resolver_rule{% #aws_route53resolver_resolver_rule %}

## `account_id`{% #account_id %}

**Type**: `STRING`

## `arn`{% #arn %}

**Type**: `STRING`**Provider name**: `Arn`**Description**: The ARN (Amazon Resource Name) for the Resolver rule specified by `Id`.

## `creation_time`{% #creation_time %}

**Type**: `STRING`**Provider name**: `CreationTime`**Description**: The date and time that the Resolver rule was created, in Unix time format and Coordinated Universal Time (UTC).

## `creator_request_id`{% #creator_request_id %}

**Type**: `STRING`**Provider name**: `CreatorRequestId`**Description**: A unique string that you specified when you created the Resolver rule. `CreatorRequestId` identifies the request and allows failed requests to be retried without the risk of running the operation twice.

## `delegation_record`{% #delegation_record %}

**Type**: `STRING`**Provider name**: `DelegationRecord`**Description**: DNS queries with delegation records that point to this domain name are forwarded to resolvers on your network.

## `domain_name`{% #domain_name %}

**Type**: `STRING`**Provider name**: `DomainName`**Description**: DNS queries for this domain name are forwarded to the IP addresses that are specified in `TargetIps`. If a query matches multiple Resolver rules (example.com and [www.example.com](https://www.example.com)), the query is routed using the Resolver rule that contains the most specific domain name ([www.example.com](https://www.example.com)).

## `id`{% #id %}

**Type**: `STRING`**Provider name**: `Id`**Description**: The ID that Resolver assigned to the Resolver rule when you created it.

## `modification_time`{% #modification_time %}

**Type**: `STRING`**Provider name**: `ModificationTime`**Description**: The date and time that the Resolver rule was last updated, in Unix time format and Coordinated Universal Time (UTC).

## `name`{% #name %}

**Type**: `STRING`**Provider name**: `Name`**Description**: The name for the Resolver rule, which you specified when you created the Resolver rule.

## `owner_id`{% #owner_id %}

**Type**: `STRING`**Provider name**: `OwnerId`**Description**: When a rule is shared with another Amazon Web Services account, the account ID of the account that the rule is shared with.

## `resolver_endpoint_id`{% #resolver_endpoint_id %}

**Type**: `STRING`**Provider name**: `ResolverEndpointId`**Description**: The ID of the endpoint that the rule is associated with.

## `rule_type`{% #rule_type %}

**Type**: `STRING`**Provider name**: `RuleType`**Description**: When you want to forward DNS queries for specified domain name to resolvers on your network, specify `FORWARD` or `DELEGATE`. If a query matches multiple Resolver rules (example.com and [www.example.com](https://www.example.com)), outbound DNS queries are routed using the Resolver rule that contains the most specific domain name ([www.example.com](https://www.example.com)). When you have a forwarding rule to forward DNS queries for a domain to your network and you want Resolver to process queries for a subdomain of that domain, specify `SYSTEM`. For example, to forward DNS queries for example.com to resolvers on your network, you create a rule and specify `FORWARD` for `RuleType`. To then have Resolver process queries for apex.example.com, you create a rule and specify `SYSTEM` for `RuleType`. Currently, only Resolver can create rules that have a value of `RECURSIVE` for `RuleType`.

## `share_status`{% #share_status %}

**Type**: `STRING`**Provider name**: `ShareStatus`**Description**: Whether the rule is shared and, if so, whether the current account is sharing the rule with another account, or another account is sharing the rule with the current account.

## `status`{% #status %}

**Type**: `STRING`**Provider name**: `Status`**Description**: A code that specifies the current status of the Resolver rule.

## `status_message`{% #status_message %}

**Type**: `STRING`**Provider name**: `StatusMessage`**Description**: A detailed description of the status of a Resolver rule.

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`

## `target_ips`{% #target_ips %}

**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `TargetIps`**Description**: An array that contains the IP addresses and ports that an outbound endpoint forwards DNS queries to. Typically, these are the IP addresses of DNS resolvers on your network.

- `ip`**Type**: `STRING`**Provider name**: `Ip`**Description**: One IPv4 address that you want to forward DNS queries to.
- `ipv6`**Type**: `STRING`**Provider name**: `Ipv6`**Description**: One IPv6 address that you want to forward DNS queries to.
- `port`**Type**: `INT32`**Provider name**: `Port`**Description**: The port at `Ip` that you want to forward DNS queries to.
- `protocol`**Type**: `STRING`**Provider name**: `Protocol`**Description**: The protocols for the target address. The protocol you choose needs to be supported by the outbound endpoint of the Resolver rule.
- `server_name_indication`**Type**: `STRING`**Provider name**: `ServerNameIndication`**Description**: The Server Name Indication of the DoH server that you want to forward queries to. This is only used if the Protocol of the `TargetAddress` is `DoH`.