View a markdown version of this page

AWS::Route53Resolver::ResolverEndpoint IpAddressRequest - AWS CloudFormation
SyntaxPropertiesSee also

This is the new CloudFormation Template Reference Guide. Please update your bookmarks and links. For help getting started with CloudFormation, see the AWS CloudFormation User Guide.

AWS::Route53Resolver::ResolverEndpoint IpAddressRequest

In a CreateResolverEndpoint request, the IP address that DNS queries originate from (for outbound endpoints) or that you forward DNS queries to (for inbound endpoints). IpAddressRequest also includes the ID of the subnet that contains the IP address.

Syntax

To declare this entity in your CloudFormation template, use the following syntax:

JSON

{
  "Ip" : String,
  "Ipv6" : String,
  "SubnetId" : String
}

YAML

  Ip: String
  Ipv6: String
  SubnetId: String

Properties

Ip

The IPv4 address that you want to use for DNS queries.

Required: No

Type: String

Minimum: 7

Maximum: 36

Update requires: No interruption

Ipv6

The IPv6 address that you want to use for DNS queries.

Required: No

Type: String

Minimum: 7

Maximum: 39

Update requires: No interruption

SubnetId

The ID of the subnet that contains the IP address.

We recommend using VPC Resolver on AWS Outposts to create endpoints on AWS Outposts Racks.

Important

Outposts subnets with Local Network Interface (LNI) enabled are not compatible with Route 53 Resolver endpoints. If you enable LNI on a subnet that contains Route 53 Resolver endpoint elastic network interfaces (ENIs), those ENIs will stop functioning. For more information, see Subnet compatibility for Resolver endpoints in the Amazon Route 53 Developer Guide.

Required: Yes

Type: String

Minimum: 1

Maximum: 32

Update requires: No interruption

See also