update_resolver_endpoint
async
¶
update_resolver_endpoint(
resolver_endpoint_id: ResourceId,
*,
config_overrides: Optional[AsyncRoute53ResolverClientConfig] = None,
name: Optional[Name] = None,
resolver_endpoint_type: Optional[ResolverEndpointType] = None,
update_ip_addresses: Optional[UpdateIpAddresses] = None,
protocols: Optional[ProtocolList] = None,
rni_enhanced_metrics_enabled: Optional[RniEnhancedMetricsEnabled] = None,
target_name_server_metrics_enabled: Optional[TargetNameServerMetricsEnabled] = None,
dns64_enabled: Optional[Dns64Enabled] = None,
ipv6_internet_access_enabled: Optional[Ipv6InternetAccessEnabled] = None,
) -> UpdateResolverEndpointResponse
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.
Parameters:
-
resolver_endpoint_id(ResourceId) –The ID of the Resolver endpoint that you want to update.
-
name(Optional[Name], default:None) –The name of the Resolver endpoint that you want to update.
-
resolver_endpoint_type(Optional[ResolverEndpointType], default:None) –Specifies the endpoint type for what type of IP address the endpoint uses to forward DNS queries.
Updating to
IPV6type isn't currently supported. -
update_ip_addresses(Optional[UpdateIpAddresses], default:None) –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(Optional[ProtocolList], default:None) –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.
-
-
rni_enhanced_metrics_enabled(Optional[RniEnhancedMetricsEnabled], default:None) –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.
-
target_name_server_metrics_enabled(Optional[TargetNameServerMetricsEnabled], default:None) –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.
-
dns64_enabled(Optional[Dns64Enabled], default:None) –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 the64:ff9b::/96prefix 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. -
ipv6_internet_access_enabled(Optional[Ipv6InternetAccessEnabled], default:None) –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.
Raises:
-
AccessDeniedException–The current account doesn't have the IAM permissions required to perform the specified Resolver operation.
This error can also be thrown when a customer has reached the 5120 character limit for a resource policy for CloudWatch Logs.
-
InternalServiceErrorException–We encountered an unknown error. Try again in a few minutes.
-
InvalidParameterException–One or more parameters in this request are not valid.
-
InvalidRequestException–The request is invalid.
-
ResourceNotFoundException–The specified resource doesn't exist.
-
ThrottlingException–The request was throttled. Try again in a few minutes.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_route53resolver/_services/async_route53_resolver.py
4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 | |