1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286
// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
/// <p>A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling <code>ListAvailableManagedRuleGroups</code>.</p>
/// <p>You cannot nest a <code>ManagedRuleGroupStatement</code>, for example for use inside a <code>NotStatement</code> or <code>OrStatement</code>. You cannot use a managed rule group inside another rule group. You can only reference a managed rule group as a top-level statement within a rule that you define in a web ACL.</p><note>
/// <p>You are charged additional fees when you use the WAF Bot Control managed rule group <code>AWSManagedRulesBotControlRuleSet</code>, the WAF Fraud Control account takeover prevention (ATP) managed rule group <code>AWSManagedRulesATPRuleSet</code>, or the WAF Fraud Control account creation fraud prevention (ACFP) managed rule group <code>AWSManagedRulesACFPRuleSet</code>. For more information, see <a href="http://aws.amazon.com/waf/pricing/">WAF Pricing</a>.</p>
/// </note>
#[non_exhaustive]
#[derive(::std::clone::Clone, ::std::cmp::PartialEq, ::std::fmt::Debug)]
pub struct ManagedRuleGroupStatement {
/// <p>The name of the managed rule group vendor. You use this, along with the rule group name, to identify a rule group.</p>
pub vendor_name: ::std::string::String,
/// <p>The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.</p>
pub name: ::std::string::String,
/// <p>The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.</p>
pub version: ::std::option::Option<::std::string::String>,
/// <p>Rules in the referenced rule group whose actions are set to <code>Count</code>.</p><note>
/// <p>Instead of this option, use <code>RuleActionOverrides</code>. It accepts any valid action setting, including <code>Count</code>.</p>
/// </note>
pub excluded_rules: ::std::option::Option<::std::vec::Vec<crate::types::ExcludedRule>>,
/// <p>An optional nested statement that narrows the scope of the web requests that are evaluated by the managed rule group. Requests are only evaluated by the rule group if they match the scope-down statement. You can use any nestable <code>Statement</code> in the scope-down statement, and you can nest statements at any level, the same as you can for a rule statement.</p>
pub scope_down_statement: ::std::option::Option<::std::boxed::Box<crate::types::Statement>>,
/// <p>Additional information that's used by a managed rule group. Many managed rule groups don't require this.</p>
/// <p>The rule groups used for intelligent threat mitigation require additional configuration:</p>
/// <ul>
/// <li>
/// <p>Use the <code>AWSManagedRulesACFPRuleSet</code> configuration object to configure the account creation fraud prevention managed rule group. The configuration includes the registration and sign-up pages of your application and the locations in the account creation request payload of data, such as the user email and phone number fields.</p></li>
/// <li>
/// <p>Use the <code>AWSManagedRulesATPRuleSet</code> configuration object to configure the account takeover prevention managed rule group. The configuration includes the sign-in page of your application and the locations in the login request payload of data such as the username and password.</p></li>
/// <li>
/// <p>Use the <code>AWSManagedRulesBotControlRuleSet</code> configuration object to configure the protection level that you want the Bot Control rule group to use.</p></li>
/// </ul>
pub managed_rule_group_configs: ::std::option::Option<::std::vec::Vec<crate::types::ManagedRuleGroupConfig>>,
/// <p>Action settings to use in the place of the rule actions that are configured inside the rule group. You specify one override for each rule whose action you want to change.</p>
/// <p>You can use overrides for testing, for example you can override all of rule actions to <code>Count</code> and then monitor the resulting count metrics to understand how the rule group would handle your web traffic. You can also permanently override some or all actions, to modify how the rule group manages your web traffic.</p>
pub rule_action_overrides: ::std::option::Option<::std::vec::Vec<crate::types::RuleActionOverride>>,
}
impl ManagedRuleGroupStatement {
/// <p>The name of the managed rule group vendor. You use this, along with the rule group name, to identify a rule group.</p>
pub fn vendor_name(&self) -> &str {
use std::ops::Deref;
self.vendor_name.deref()
}
/// <p>The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.</p>
pub fn name(&self) -> &str {
use std::ops::Deref;
self.name.deref()
}
/// <p>The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.</p>
pub fn version(&self) -> ::std::option::Option<&str> {
self.version.as_deref()
}
/// <p>Rules in the referenced rule group whose actions are set to <code>Count</code>.</p><note>
/// <p>Instead of this option, use <code>RuleActionOverrides</code>. It accepts any valid action setting, including <code>Count</code>.</p>
/// </note>
///
/// If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use `.excluded_rules.is_none()`.
pub fn excluded_rules(&self) -> &[crate::types::ExcludedRule] {
self.excluded_rules.as_deref().unwrap_or_default()
}
/// <p>An optional nested statement that narrows the scope of the web requests that are evaluated by the managed rule group. Requests are only evaluated by the rule group if they match the scope-down statement. You can use any nestable <code>Statement</code> in the scope-down statement, and you can nest statements at any level, the same as you can for a rule statement.</p>
pub fn scope_down_statement(&self) -> ::std::option::Option<&crate::types::Statement> {
self.scope_down_statement.as_deref()
}
/// <p>Additional information that's used by a managed rule group. Many managed rule groups don't require this.</p>
/// <p>The rule groups used for intelligent threat mitigation require additional configuration:</p>
/// <ul>
/// <li>
/// <p>Use the <code>AWSManagedRulesACFPRuleSet</code> configuration object to configure the account creation fraud prevention managed rule group. The configuration includes the registration and sign-up pages of your application and the locations in the account creation request payload of data, such as the user email and phone number fields.</p></li>
/// <li>
/// <p>Use the <code>AWSManagedRulesATPRuleSet</code> configuration object to configure the account takeover prevention managed rule group. The configuration includes the sign-in page of your application and the locations in the login request payload of data such as the username and password.</p></li>
/// <li>
/// <p>Use the <code>AWSManagedRulesBotControlRuleSet</code> configuration object to configure the protection level that you want the Bot Control rule group to use.</p></li>
/// </ul>
///
/// If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use `.managed_rule_group_configs.is_none()`.
pub fn managed_rule_group_configs(&self) -> &[crate::types::ManagedRuleGroupConfig] {
self.managed_rule_group_configs.as_deref().unwrap_or_default()
}
/// <p>Action settings to use in the place of the rule actions that are configured inside the rule group. You specify one override for each rule whose action you want to change.</p>
/// <p>You can use overrides for testing, for example you can override all of rule actions to <code>Count</code> and then monitor the resulting count metrics to understand how the rule group would handle your web traffic. You can also permanently override some or all actions, to modify how the rule group manages your web traffic.</p>
///
/// If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use `.rule_action_overrides.is_none()`.
pub fn rule_action_overrides(&self) -> &[crate::types::RuleActionOverride] {
self.rule_action_overrides.as_deref().unwrap_or_default()
}
}
impl ManagedRuleGroupStatement {
/// Creates a new builder-style object to manufacture [`ManagedRuleGroupStatement`](crate::types::ManagedRuleGroupStatement).
pub fn builder() -> crate::types::builders::ManagedRuleGroupStatementBuilder {
crate::types::builders::ManagedRuleGroupStatementBuilder::default()
}
}
/// A builder for [`ManagedRuleGroupStatement`](crate::types::ManagedRuleGroupStatement).
#[non_exhaustive]
#[derive(::std::clone::Clone, ::std::cmp::PartialEq, ::std::default::Default, ::std::fmt::Debug)]
pub struct ManagedRuleGroupStatementBuilder {
pub(crate) vendor_name: ::std::option::Option<::std::string::String>,
pub(crate) name: ::std::option::Option<::std::string::String>,
pub(crate) version: ::std::option::Option<::std::string::String>,
pub(crate) excluded_rules: ::std::option::Option<::std::vec::Vec<crate::types::ExcludedRule>>,
pub(crate) scope_down_statement: ::std::option::Option<::std::boxed::Box<crate::types::Statement>>,
pub(crate) managed_rule_group_configs: ::std::option::Option<::std::vec::Vec<crate::types::ManagedRuleGroupConfig>>,
pub(crate) rule_action_overrides: ::std::option::Option<::std::vec::Vec<crate::types::RuleActionOverride>>,
}
impl ManagedRuleGroupStatementBuilder {
/// <p>The name of the managed rule group vendor. You use this, along with the rule group name, to identify a rule group.</p>
/// This field is required.
pub fn vendor_name(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.vendor_name = ::std::option::Option::Some(input.into());
self
}
/// <p>The name of the managed rule group vendor. You use this, along with the rule group name, to identify a rule group.</p>
pub fn set_vendor_name(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.vendor_name = input;
self
}
/// <p>The name of the managed rule group vendor. You use this, along with the rule group name, to identify a rule group.</p>
pub fn get_vendor_name(&self) -> &::std::option::Option<::std::string::String> {
&self.vendor_name
}
/// <p>The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.</p>
/// This field is required.
pub fn name(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.name = ::std::option::Option::Some(input.into());
self
}
/// <p>The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.</p>
pub fn set_name(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.name = input;
self
}
/// <p>The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.</p>
pub fn get_name(&self) -> &::std::option::Option<::std::string::String> {
&self.name
}
/// <p>The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.</p>
pub fn version(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.version = ::std::option::Option::Some(input.into());
self
}
/// <p>The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.</p>
pub fn set_version(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.version = input;
self
}
/// <p>The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.</p>
pub fn get_version(&self) -> &::std::option::Option<::std::string::String> {
&self.version
}
/// Appends an item to `excluded_rules`.
///
/// To override the contents of this collection use [`set_excluded_rules`](Self::set_excluded_rules).
///
/// <p>Rules in the referenced rule group whose actions are set to <code>Count</code>.</p><note>
/// <p>Instead of this option, use <code>RuleActionOverrides</code>. It accepts any valid action setting, including <code>Count</code>.</p>
/// </note>
pub fn excluded_rules(mut self, input: crate::types::ExcludedRule) -> Self {
let mut v = self.excluded_rules.unwrap_or_default();
v.push(input);
self.excluded_rules = ::std::option::Option::Some(v);
self
}
/// <p>Rules in the referenced rule group whose actions are set to <code>Count</code>.</p><note>
/// <p>Instead of this option, use <code>RuleActionOverrides</code>. It accepts any valid action setting, including <code>Count</code>.</p>
/// </note>
pub fn set_excluded_rules(mut self, input: ::std::option::Option<::std::vec::Vec<crate::types::ExcludedRule>>) -> Self {
self.excluded_rules = input;
self
}
/// <p>Rules in the referenced rule group whose actions are set to <code>Count</code>.</p><note>
/// <p>Instead of this option, use <code>RuleActionOverrides</code>. It accepts any valid action setting, including <code>Count</code>.</p>
/// </note>
pub fn get_excluded_rules(&self) -> &::std::option::Option<::std::vec::Vec<crate::types::ExcludedRule>> {
&self.excluded_rules
}
/// <p>An optional nested statement that narrows the scope of the web requests that are evaluated by the managed rule group. Requests are only evaluated by the rule group if they match the scope-down statement. You can use any nestable <code>Statement</code> in the scope-down statement, and you can nest statements at any level, the same as you can for a rule statement.</p>
pub fn scope_down_statement(mut self, input: impl ::std::convert::Into<::std::boxed::Box<crate::types::Statement>>) -> Self {
self.scope_down_statement = ::std::option::Option::Some(input.into());
self
}
/// <p>An optional nested statement that narrows the scope of the web requests that are evaluated by the managed rule group. Requests are only evaluated by the rule group if they match the scope-down statement. You can use any nestable <code>Statement</code> in the scope-down statement, and you can nest statements at any level, the same as you can for a rule statement.</p>
pub fn set_scope_down_statement(mut self, input: ::std::option::Option<::std::boxed::Box<crate::types::Statement>>) -> Self {
self.scope_down_statement = input;
self
}
/// <p>An optional nested statement that narrows the scope of the web requests that are evaluated by the managed rule group. Requests are only evaluated by the rule group if they match the scope-down statement. You can use any nestable <code>Statement</code> in the scope-down statement, and you can nest statements at any level, the same as you can for a rule statement.</p>
pub fn get_scope_down_statement(&self) -> &::std::option::Option<::std::boxed::Box<crate::types::Statement>> {
&self.scope_down_statement
}
/// Appends an item to `managed_rule_group_configs`.
///
/// To override the contents of this collection use [`set_managed_rule_group_configs`](Self::set_managed_rule_group_configs).
///
/// <p>Additional information that's used by a managed rule group. Many managed rule groups don't require this.</p>
/// <p>The rule groups used for intelligent threat mitigation require additional configuration:</p>
/// <ul>
/// <li>
/// <p>Use the <code>AWSManagedRulesACFPRuleSet</code> configuration object to configure the account creation fraud prevention managed rule group. The configuration includes the registration and sign-up pages of your application and the locations in the account creation request payload of data, such as the user email and phone number fields.</p></li>
/// <li>
/// <p>Use the <code>AWSManagedRulesATPRuleSet</code> configuration object to configure the account takeover prevention managed rule group. The configuration includes the sign-in page of your application and the locations in the login request payload of data such as the username and password.</p></li>
/// <li>
/// <p>Use the <code>AWSManagedRulesBotControlRuleSet</code> configuration object to configure the protection level that you want the Bot Control rule group to use.</p></li>
/// </ul>
pub fn managed_rule_group_configs(mut self, input: crate::types::ManagedRuleGroupConfig) -> Self {
let mut v = self.managed_rule_group_configs.unwrap_or_default();
v.push(input);
self.managed_rule_group_configs = ::std::option::Option::Some(v);
self
}
/// <p>Additional information that's used by a managed rule group. Many managed rule groups don't require this.</p>
/// <p>The rule groups used for intelligent threat mitigation require additional configuration:</p>
/// <ul>
/// <li>
/// <p>Use the <code>AWSManagedRulesACFPRuleSet</code> configuration object to configure the account creation fraud prevention managed rule group. The configuration includes the registration and sign-up pages of your application and the locations in the account creation request payload of data, such as the user email and phone number fields.</p></li>
/// <li>
/// <p>Use the <code>AWSManagedRulesATPRuleSet</code> configuration object to configure the account takeover prevention managed rule group. The configuration includes the sign-in page of your application and the locations in the login request payload of data such as the username and password.</p></li>
/// <li>
/// <p>Use the <code>AWSManagedRulesBotControlRuleSet</code> configuration object to configure the protection level that you want the Bot Control rule group to use.</p></li>
/// </ul>
pub fn set_managed_rule_group_configs(mut self, input: ::std::option::Option<::std::vec::Vec<crate::types::ManagedRuleGroupConfig>>) -> Self {
self.managed_rule_group_configs = input;
self
}
/// <p>Additional information that's used by a managed rule group. Many managed rule groups don't require this.</p>
/// <p>The rule groups used for intelligent threat mitigation require additional configuration:</p>
/// <ul>
/// <li>
/// <p>Use the <code>AWSManagedRulesACFPRuleSet</code> configuration object to configure the account creation fraud prevention managed rule group. The configuration includes the registration and sign-up pages of your application and the locations in the account creation request payload of data, such as the user email and phone number fields.</p></li>
/// <li>
/// <p>Use the <code>AWSManagedRulesATPRuleSet</code> configuration object to configure the account takeover prevention managed rule group. The configuration includes the sign-in page of your application and the locations in the login request payload of data such as the username and password.</p></li>
/// <li>
/// <p>Use the <code>AWSManagedRulesBotControlRuleSet</code> configuration object to configure the protection level that you want the Bot Control rule group to use.</p></li>
/// </ul>
pub fn get_managed_rule_group_configs(&self) -> &::std::option::Option<::std::vec::Vec<crate::types::ManagedRuleGroupConfig>> {
&self.managed_rule_group_configs
}
/// Appends an item to `rule_action_overrides`.
///
/// To override the contents of this collection use [`set_rule_action_overrides`](Self::set_rule_action_overrides).
///
/// <p>Action settings to use in the place of the rule actions that are configured inside the rule group. You specify one override for each rule whose action you want to change.</p>
/// <p>You can use overrides for testing, for example you can override all of rule actions to <code>Count</code> and then monitor the resulting count metrics to understand how the rule group would handle your web traffic. You can also permanently override some or all actions, to modify how the rule group manages your web traffic.</p>
pub fn rule_action_overrides(mut self, input: crate::types::RuleActionOverride) -> Self {
let mut v = self.rule_action_overrides.unwrap_or_default();
v.push(input);
self.rule_action_overrides = ::std::option::Option::Some(v);
self
}
/// <p>Action settings to use in the place of the rule actions that are configured inside the rule group. You specify one override for each rule whose action you want to change.</p>
/// <p>You can use overrides for testing, for example you can override all of rule actions to <code>Count</code> and then monitor the resulting count metrics to understand how the rule group would handle your web traffic. You can also permanently override some or all actions, to modify how the rule group manages your web traffic.</p>
pub fn set_rule_action_overrides(mut self, input: ::std::option::Option<::std::vec::Vec<crate::types::RuleActionOverride>>) -> Self {
self.rule_action_overrides = input;
self
}
/// <p>Action settings to use in the place of the rule actions that are configured inside the rule group. You specify one override for each rule whose action you want to change.</p>
/// <p>You can use overrides for testing, for example you can override all of rule actions to <code>Count</code> and then monitor the resulting count metrics to understand how the rule group would handle your web traffic. You can also permanently override some or all actions, to modify how the rule group manages your web traffic.</p>
pub fn get_rule_action_overrides(&self) -> &::std::option::Option<::std::vec::Vec<crate::types::RuleActionOverride>> {
&self.rule_action_overrides
}
/// Consumes the builder and constructs a [`ManagedRuleGroupStatement`](crate::types::ManagedRuleGroupStatement).
/// This method will fail if any of the following fields are not set:
/// - [`vendor_name`](crate::types::builders::ManagedRuleGroupStatementBuilder::vendor_name)
/// - [`name`](crate::types::builders::ManagedRuleGroupStatementBuilder::name)
pub fn build(self) -> ::std::result::Result<crate::types::ManagedRuleGroupStatement, ::aws_smithy_types::error::operation::BuildError> {
::std::result::Result::Ok(crate::types::ManagedRuleGroupStatement {
vendor_name: self.vendor_name.ok_or_else(|| {
::aws_smithy_types::error::operation::BuildError::missing_field(
"vendor_name",
"vendor_name was not specified but it is required when building ManagedRuleGroupStatement",
)
})?,
name: self.name.ok_or_else(|| {
::aws_smithy_types::error::operation::BuildError::missing_field(
"name",
"name was not specified but it is required when building ManagedRuleGroupStatement",
)
})?,
version: self.version,
excluded_rules: self.excluded_rules,
scope_down_statement: self.scope_down_statement,
managed_rule_group_configs: self.managed_rule_group_configs,
rule_action_overrides: self.rule_action_overrides,
})
}
}