route53resolver_create_resolver_endpoint: Creates a Resolver endpoint
In paws.networking: 'Amazon Web Services' Networking & Content Delivery Services

View source: R/route53resolver_operations.R

route53resolver_create_resolver_endpoint

R Documentation

Creates a Resolver endpoint

Description

Creates a Resolver endpoint. There are two types of Resolver endpoints, inbound and outbound:

See https://www.paws-r-sdk.com/docs/route53resolver_create_resolver_endpoint/ for full documentation.

Usage

route53resolver_create_resolver_endpoint(
  CreatorRequestId,
  Name = NULL,
  SecurityGroupIds,
  Direction,
  IpAddresses,
  OutpostArn = NULL,
  PreferredInstanceType = NULL,
  Tags = NULL,
  ResolverEndpointType = NULL,
  Protocols = NULL
)

Arguments

`CreatorRequestId`	[required] A unique string that identifies the request and that allows failed requests to be retried without the risk of running the operation twice. `CreatorRequestId` can be any unique string, for example, a date/time stamp.
`Name`	A friendly name that lets you easily find a configuration in the Resolver dashboard in the Route 53 console.
`SecurityGroupIds`	[required] The ID of one or more security groups that you want to use to control access to this VPC. The security group that you specify must include one or more inbound rules (for inbound Resolver endpoints) or outbound rules (for outbound Resolver endpoints). Inbound and outbound rules must allow TCP and UDP access. For inbound access, open port 53. For outbound access, open the port that you're using for DNS queries on your network. Some security group rules will cause your connection to be tracked. For outbound resolver endpoint, it can potentially impact the maximum queries per second from outbound endpoint to your target name server. For inbound resolver endpoint, it can bring down the overall maximum queries per second per IP address to as low as 1500. To avoid connection tracking caused by security group, see Untracked connections.
`Direction`	[required] Specify the applicable value: `INBOUND`: Resolver forwards DNS queries to the DNS service for a VPC from your network `OUTBOUND`: Resolver forwards DNS queries from the DNS service for a VPC to your network
`IpAddresses`	[required] The subnets and IP addresses in your VPC that DNS queries originate from (for outbound endpoints) or that you forward DNS queries to (for inbound endpoints). The subnet ID uniquely identifies a VPC. Even though the minimum is 1, Route 53 requires that you create at least two.
`OutpostArn`	The Amazon Resource Name (ARN) of the Outpost. If you specify this, you must also specify a value for the `PreferredInstanceType`.
`PreferredInstanceType`	The instance type. If you specify this, you must also specify a value for the `OutpostArn`.
`Tags`	A list of the tag keys and values that you want to associate with the endpoint.
`ResolverEndpointType`	For the endpoint type you can choose either IPv4, IPv6, or dual-stack. A dual-stack endpoint means that it will resolve via both IPv4 and IPv6. This endpoint type is applied to all IP addresses.
`Protocols`	The protocols you want to use for the endpoint. DoH-FIPS is applicable for inbound endpoints only. For an inbound endpoint you can apply the protocols as follows: Do53 and DoH in combination. Do53 and DoH-FIPS in combination. Do53 alone. DoH alone. DoH-FIPS alone. None, which is treated as Do53. For an outbound endpoint you can apply the protocols as follows: Do53 and DoH in combination. Do53 alone. DoH alone. None, which is treated as Do53.