associate_resolver_rule
¶
associate_resolver_rule(
resolver_rule_id: ResourceId,
vpc_id: ResourceId,
*,
config_overrides: Optional[Route53ResolverClientConfig] = None,
name: Optional[Name] = None,
) -> AssociateResolverRuleResponse
Associates a Resolver rule with a VPC. When you associate a rule with a VPC, Resolver forwards all DNS queries for the domain name that is specified in the rule and that originate in the VPC. The queries are forwarded to the IP addresses for the DNS resolvers that are specified in the rule. For more information about rules, see CreateResolverRule.
Parameters:
-
resolver_rule_id(ResourceId) –The ID of the Resolver rule that you want to associate with the VPC. To list the existing Resolver rules, use ListResolverRules.
-
name(Optional[Name], default:None) –A name for the association that you're creating between a Resolver rule and a VPC.
The name can be up to 64 characters long and can contain letters (a-z, A-Z), numbers (0-9), hyphens (-), underscores (_), and spaces. The name cannot consist of only numbers.
-
vpc_id(ResourceId) –The ID of the VPC that you want to associate the Resolver rule with.
Raises:
-
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.
-
LimitExceededException–The request caused one or more limits to be exceeded.
-
ResourceExistsException–The resource that you tried to create already exists.
-
ResourceNotFoundException–The specified resource doesn't exist.
-
ResourceUnavailableException–The specified resource isn't available.
-
ThrottlingException–The request was throttled. Try again in a few minutes.
-
UnknownServiceError–The service returned an error code this client does not model.