Skip to content

Update Resolver Endpoint

route53resolver_update_resolver_endpoint R Documentation

Updates the name, or endpoint type for an inbound or an outbound Resolver endpoint

Description

Updates the name, or endpoint type for an inbound or an outbound Resolver endpoint. You can only update between IPV4 and DUALSTACK, IPV6 endpoint type can't be updated to other type.

Usage

route53resolver_update_resolver_endpoint(ResolverEndpointId, Name,
  ResolverEndpointType, UpdateIpAddresses, Protocols,
  RniEnhancedMetricsEnabled, TargetNameServerMetricsEnabled, Dns64Enabled,
  Ipv6InternetAccessEnabled)

Arguments

ResolverEndpointId

[required] The ID of the Resolver endpoint that you want to update.
Name

The name of the Resolver endpoint that you want to update.
ResolverEndpointType

Specifies the endpoint type for what type of IP address the endpoint uses to forward DNS queries.

Updating to IPV6 type isn't currently supported.
UpdateIpAddresses

Specifies the IPv6 address when you update the Resolver endpoint from IPv4 to dual-stack. If you don't specify an IPv6 address, one will be automatically chosen from your subnet.
Protocols

The protocols you want to use for the endpoint. DoH-FIPS is applicable for default inbound endpoints only.

For a default 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 a delegation inbound endpoint you can use Do53 only.

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.

You can't change the protocol of an inbound endpoint directly from only Do53 to only DoH, or DoH-FIPS. This is to prevent a sudden disruption to incoming traffic that relies on Do53. To change the protocol from Do53 to DoH, or DoH-FIPS, you must first enable both Do53 and DoH, or Do53 and DoH-FIPS, to make sure that all incoming traffic has transferred to using the DoH protocol, or DoH-FIPS, and then remove the Do53.
RniEnhancedMetricsEnabled

Updates whether RNI enhanced metrics are enabled for the Resolver endpoints. When set to true, one-minute granular metrics are published in CloudWatch for each RNI associated with this endpoint. When set to false, metrics are not published.

Standard CloudWatch pricing and charges are applied for using the Route 53 Resolver endpoint RNI enhanced metrics. For more information, see Detailed metrics.
TargetNameServerMetricsEnabled

Updates whether target name server metrics are enabled for the outbound Resolver endpoints. When set to true, one-minute granular metrics are published in CloudWatch for each target name server associated with this endpoint. When set to false, metrics are not published. This setting is not supported for inbound Resolver endpoints.

Standard CloudWatch pricing and charges are applied for using the Route 53 Resolver endpoint target name server metrics. For more information, see Detailed metrics.
Dns64Enabled

Specifies whether DNS64 is enabled for the inbound Resolver endpoint. When set to true, Route 53 Resolver synthesizes AAAA (IPv6) records for IPv4-only services by prepending the ⁠64:ff9b::/96⁠ prefix to the IPv4 address. This enables IPv6-only clients that send queries through the inbound endpoint to reach IPv4-only services. DNS64 works with NAT64 to provide complete IPv6-to-IPv4 translation.
Ipv6InternetAccessEnabled

Specifies whether IPv6 internet access is enabled for the outbound Resolver endpoint. When set to true, the endpoint elastic network interfaces (ENIs) can forward DNS queries to public IPv6 targets through an internet gateway.

When you enable IPv6 internet access, use network controls like security groups, NACLs, or egress-only internet gateways to protect the endpoint ENIs from unsolicited ingress traffic. Be aware that some network controls can affect DNS query throughput due to connection tracking. For more information, see Amazon EC2 security group connection tracking and Resolver endpoint scaling.

Value

A list with the following syntax:

list(
  ResolverEndpoint = list(
    Id = "string",
    CreatorRequestId = "string",
    Arn = "string",
    Name = "string",
    SecurityGroupIds = list(
      "string"
    ),
    Direction = "INBOUND"|"OUTBOUND"|"INBOUND_DELEGATION",
    IpAddressCount = 123,
    HostVPCId = "string",
    Status = "CREATING"|"OPERATIONAL"|"UPDATING"|"AUTO_RECOVERING"|"ACTION_NEEDED"|"DELETING",
    StatusMessage = "string",
    CreationTime = "string",
    ModificationTime = "string",
    OutpostArn = "string",
    PreferredInstanceType = "string",
    ResolverEndpointType = "IPV6"|"IPV4"|"DUALSTACK",
    Protocols = list(
      "DoH"|"Do53"|"DoH-FIPS"
    ),
    RniEnhancedMetricsEnabled = TRUE|FALSE,
    TargetNameServerMetricsEnabled = TRUE|FALSE,
    Dns64Enabled = TRUE|FALSE,
    Ipv6InternetAccessEnabled = TRUE|FALSE
  )
)

Request syntax

svc$update_resolver_endpoint(
  ResolverEndpointId = "string",
  Name = "string",
  ResolverEndpointType = "IPV6"|"IPV4"|"DUALSTACK",
  UpdateIpAddresses = list(
    list(
      IpId = "string",
      Ipv6 = "string"
    )
  ),
  Protocols = list(
    "DoH"|"Do53"|"DoH-FIPS"
  ),
  RniEnhancedMetricsEnabled = TRUE|FALSE,
  TargetNameServerMetricsEnabled = TRUE|FALSE,
  Dns64Enabled = TRUE|FALSE,
  Ipv6InternetAccessEnabled = TRUE|FALSE
)