Struct aws_sdk_route53resolver::input::CreateResolverRuleInput

#[non_exhaustive]
pub struct CreateResolverRuleInput {
    pub creator_request_id: Option<String>,
    pub name: Option<String>,
    pub rule_type: Option<RuleTypeOption>,
    pub domain_name: Option<String>,
    pub target_ips: Option<Vec<TargetAddress>>,
    pub resolver_endpoint_id: Option<String>,
    pub tags: Option<Vec<Tag>>,
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

creator_request_id: Option<String>

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: Option<String>

A friendly name that lets you easily find a rule in the Resolver dashboard in the Route 53 console.

rule_type: Option<RuleTypeOption>

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.

For example, to forward DNS queries for example.com to resolvers on your network, you create a rule and specify FORWARD for RuleType. To then have Resolver process queries for apex.example.com, you create a rule and specify SYSTEM for RuleType.

Currently, only Resolver can create rules that have a value of RECURSIVE for RuleType.

domain_name: Option<String>

DNS queries for this domain name are forwarded to the IP addresses that you specify in TargetIps. If a query matches multiple Resolver rules (example.com and www.example.com), outbound DNS queries are routed using the Resolver rule that contains the most specific domain name (www.example.com).

target_ips: Option<Vec<TargetAddress>>

The IPs that you want Resolver to forward DNS queries to. You can specify only IPv4 addresses. Separate IP addresses with a space.

TargetIps is available only when the value of Rule type is FORWARD.

resolver_endpoint_id: Option<String>

The ID of the outbound Resolver endpoint that you want to use to route DNS queries to the IP addresses that you specify in TargetIps.

tags: Option<Vec<Tag>>

A list of the tag keys and values that you want to associate with the endpoint.

Implementations

impl CreateResolverRuleInput

pub async fn make_operation(
    &self,
    _config: &Config
) -> Result<Operation<CreateResolverRule, AwsErrorRetryPolicy>, BuildError>

Consumes the builder and constructs an Operation<CreateResolverRule>

pub fn builder() -> Builder

Creates a new builder-style object to manufacture CreateResolverRuleInput

impl CreateResolverRuleInput

pub fn creator_request_id(&self) -> Option<&str>

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.

pub fn name(&self) -> Option<&str>

A friendly name that lets you easily find a rule in the Resolver dashboard in the Route 53 console.

pub fn rule_type(&self) -> Option<&RuleTypeOption>

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.

For example, to forward DNS queries for example.com to resolvers on your network, you create a rule and specify FORWARD for RuleType. To then have Resolver process queries for apex.example.com, you create a rule and specify SYSTEM for RuleType.

Currently, only Resolver can create rules that have a value of RECURSIVE for RuleType.

pub fn domain_name(&self) -> Option<&str>

DNS queries for this domain name are forwarded to the IP addresses that you specify in TargetIps. If a query matches multiple Resolver rules (example.com and www.example.com), outbound DNS queries are routed using the Resolver rule that contains the most specific domain name (www.example.com).

pub fn target_ips(&self) -> Option<&[TargetAddress]>

The IPs that you want Resolver to forward DNS queries to. You can specify only IPv4 addresses. Separate IP addresses with a space.

TargetIps is available only when the value of Rule type is FORWARD.

pub fn resolver_endpoint_id(&self) -> Option<&str>

The ID of the outbound Resolver endpoint that you want to use to route DNS queries to the IP addresses that you specify in TargetIps.

pub fn tags(&self) -> Option<&[Tag]>

A list of the tag keys and values that you want to associate with the endpoint.

Trait Implementations

impl Clone for CreateResolverRuleInput

fn clone(&self) -> CreateResolverRuleInput

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CreateResolverRuleInput

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq<CreateResolverRuleInput> for CreateResolverRuleInput

fn eq(&self, other: &CreateResolverRuleInput) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &CreateResolverRuleInput) -> bool

This method tests for !=.

impl StructuralPartialEq for CreateResolverRuleInput