Struct aws_sdk_route53resolver::client::fluent_builders::UpdateFirewallRule

pub struct UpdateFirewallRule<C = DynConnector, M = AwsMiddleware, R = Standard> { /* fields omitted */ }

Fluent builder constructing a request to UpdateFirewallRule.

Updates the specified firewall rule.

Implementations

impl<C, M, R> UpdateFirewallRule<C, M, R> where
    C: SmithyConnector,
    M: SmithyMiddleware<C>,
    R: NewRequestPolicy, 

pub async fn send(
    self
) -> Result<UpdateFirewallRuleOutput, SdkError<UpdateFirewallRuleError>> where
    R::Policy: SmithyRetryPolicy<UpdateFirewallRuleInputOperationOutputAlias, UpdateFirewallRuleOutput, UpdateFirewallRuleError, UpdateFirewallRuleInputOperationRetryAlias>, 

Sends the request and returns the response.

If an error occurs, an SdkError will be returned with additional details that can be matched against.

By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.

pub fn firewall_rule_group_id(self, inp: impl Into<String>) -> Self

The unique identifier of the firewall rule group for the rule.

pub fn set_firewall_rule_group_id(self, input: Option<String>) -> Self

The unique identifier of the firewall rule group for the rule.

pub fn firewall_domain_list_id(self, inp: impl Into<String>) -> Self

The ID of the domain list to use in the rule.

pub fn set_firewall_domain_list_id(self, input: Option<String>) -> Self

The ID of the domain list to use in the rule.

pub fn priority(self, inp: i32) -> Self

The setting that determines the processing order of the rule in the rule group. DNS Firewall processes the rules in a rule group by order of priority, starting from the lowest setting.

You must specify a unique priority for each rule in a rule group. To make it easier to insert rules later, leave space between the numbers, for example, use 100, 200, and so on. You can change the priority setting for the rules in a rule group at any time.

pub fn set_priority(self, input: Option<i32>) -> Self

The setting that determines the processing order of the rule in the rule group. DNS Firewall processes the rules in a rule group by order of priority, starting from the lowest setting.

You must specify a unique priority for each rule in a rule group. To make it easier to insert rules later, leave space between the numbers, for example, use 100, 200, and so on. You can change the priority setting for the rules in a rule group at any time.

pub fn action(self, inp: Action) -> Self

The action that DNS Firewall should take on a DNS query when it matches one of the domains in the rule's domain list:

• ALLOW - Permit the request to go through.

• ALERT - Permit the request to go through but send an alert to the logs.

• BLOCK - Disallow the request. This option requires additional details in the rule's BlockResponse.

pub fn set_action(self, input: Option<Action>) -> Self

The action that DNS Firewall should take on a DNS query when it matches one of the domains in the rule's domain list:

• ALLOW - Permit the request to go through.

• ALERT - Permit the request to go through but send an alert to the logs.

• BLOCK - Disallow the request. This option requires additional details in the rule's BlockResponse.

pub fn block_response(self, inp: BlockResponse) -> Self

The way that you want DNS Firewall to block the request. Used for the rule action setting BLOCK.

• NODATA - Respond indicating that the query was successful, but no response is available for it.

• NXDOMAIN - Respond indicating that the domain name that's in the query doesn't exist.

• OVERRIDE - Provide a custom override in the response. This option requires custom handling details in the rule's BlockOverride* settings.

pub fn set_block_response(self, input: Option<BlockResponse>) -> Self

The way that you want DNS Firewall to block the request. Used for the rule action setting BLOCK.

• NODATA - Respond indicating that the query was successful, but no response is available for it.

• NXDOMAIN - Respond indicating that the domain name that's in the query doesn't exist.

• OVERRIDE - Provide a custom override in the response. This option requires custom handling details in the rule's BlockOverride* settings.

pub fn block_override_domain(self, inp: impl Into<String>) -> Self

The custom DNS record to send back in response to the query. Used for the rule action BLOCK with a BlockResponse setting of OVERRIDE.

pub fn set_block_override_domain(self, input: Option<String>) -> Self

The custom DNS record to send back in response to the query. Used for the rule action BLOCK with a BlockResponse setting of OVERRIDE.

pub fn block_override_dns_type(self, inp: BlockOverrideDnsType) -> Self

The DNS record's type. This determines the format of the record value that you provided in BlockOverrideDomain. Used for the rule action BLOCK with a BlockResponse setting of OVERRIDE.

pub fn set_block_override_dns_type(
    self,
    input: Option<BlockOverrideDnsType>
) -> Self

The DNS record's type. This determines the format of the record value that you provided in BlockOverrideDomain. Used for the rule action BLOCK with a BlockResponse setting of OVERRIDE.

pub fn block_override_ttl(self, inp: i32) -> Self

The recommended amount of time, in seconds, for the DNS resolver or web browser to cache the provided override record. Used for the rule action BLOCK with a BlockResponse setting of OVERRIDE.

pub fn set_block_override_ttl(self, input: Option<i32>) -> Self

The recommended amount of time, in seconds, for the DNS resolver or web browser to cache the provided override record. Used for the rule action BLOCK with a BlockResponse setting of OVERRIDE.

pub fn name(self, inp: impl Into<String>) -> Self

The name of the rule.

pub fn set_name(self, input: Option<String>) -> Self

The name of the rule.

Trait Implementations

impl<C: Debug, M: Debug, R: Debug> Debug for UpdateFirewallRule<C, M, R>

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

Formats the value using the given formatter.