Readonly
domainThe domain name for the resolver rule.
Optional
Readonly
excluded(OPTIONAL) Regions to exclude from SYSTEM rule deployment.
Optional
Readonly
inbound(OPTIONAL) The friendly name of an inbound endpoint to target.
This is the logical name
property of an INBOUND endpoint as defined in network-config.yaml.
Use this property to define resolver rules for resolving DNS records across subdomains hosted within the accelerator environment. This creates a FORWARD rule that targets the IP addresses of an INBOUND endpoint.
ResolverEndpointConfig
Readonly
nameA friendly name for the resolver rule.
Optional
Readonly
rule(OPTIONAL) The type of rule to create.
CAUTION: Changing this property value after initial deployment causes the rule to be recreated. Please be aware that any downstream dependencies may cause this property update to fail.
When you want to forward DNS queries for specified domain name to resolvers on your network, specify FORWARD.
When you have a forwarding rule to forward DNS queries for a domain to your network and you want Resolver to process queries for a subdomain of that domain, specify SYSTEM.
Currently, only the Resolver service can create rules that have a value of RECURSIVE for ruleType. Do not use type RECURSIVE. This is reserved for future use.
NetworkConfigTypes.ruleTypeEnum
Optional
Readonly
share(OPTIONAL) Resource Access Manager (RAM) share targets.
Optional
Readonly
tags(OPTIONAL) An array of tags for the resolver rule.
Optional
Readonly
target(OPTIONAL) An array of target IP configurations for the resolver rule.
NetworkConfig / CentralNetworkServicesConfig / ResolverConfig / (ResolverEndpointConfig) / ResolverRuleConfig
Route 53 resolver rule configuration.
Description
Use this configuration to define resolver SYSTEM and FORWARD rules for your resolver. If you want Resolver to forward queries for specified domain names to your network, you create one forwarding rule for each domain name and specify the name of the domain for which you want to forward queries.
Remarks
FORWARD rules should be defined under an OUTBOUND ResolverEndpointConfig. SYSTEM rules should be defined directly under ResolverConfig.
The following example creates a forwarding rule for
example.com
that is shared with the entire organization. This rule targets an example on-prem IP address of1.1.1.1
.Example