Skip to content

AssociateFirewallRuleGroupRequest

Source code in docs_src/capo_route53resolver/types/associate_firewall_rule_group_request.py 
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
class AssociateFirewallRuleGroupRequest(TypedDict, closed=True):
    creator_request_id: "capo_route53resolver.types.creator_request_id.CreatorRequestId"
    """<p>A unique string that identifies the request and that allows failed requests to be retried without the risk of running the operation twice. <code>CreatorRequestId</code> can be any unique string, for example, a date/time stamp. </p>"""
    firewall_rule_group_id: "capo_route53resolver.types.resource_id.ResourceId"
    """<p>The unique identifier of the firewall rule group. </p>"""
    vpc_id: "capo_route53resolver.types.resource_id.ResourceId"
    """<p>The unique identifier of the VPC that you want to associate with the rule group. </p>"""
    priority: "capo_route53resolver.types.priority.Priority"
    """<p>The setting that determines the processing order of the rule group among the rule groups that you associate with the specified VPC. DNS Firewall filters VPC traffic starting from the rule group with the lowest numeric priority setting. </p> <p>You must specify a unique priority for each rule group that you associate with a single VPC. To make it easier to insert rule groups later, leave space between the numbers, for example, use 101, 200, and so on. You can change the priority setting for a rule group association after you create it.</p> <p>The allowed values for <code>Priority</code> are between 100 and 9900.</p>"""
    name: "capo_route53resolver.types.name.Name"
    """<p>A name that lets you identify the association, to manage and use it.</p>"""
    mutation_protection: NotRequired[
        "capo_route53resolver.types.mutation_protection_status.MutationProtectionStatus"
    ]
    """<p>If enabled, this setting disallows modification or removal of the association, to help prevent against accidentally altering DNS firewall protections. When you create the association, the default setting is <code>DISABLED</code>. </p>"""
    tags: NotRequired["capo_route53resolver.types.tag_list.TagList"]
    """<p>A list of the tag keys and values that you want to associate with the rule group association. </p>"""

creator_request_id instance-attribute 

creator_request_id: CreatorRequestId

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.

firewall_rule_group_id instance-attribute 

firewall_rule_group_id: ResourceId

The unique identifier of the firewall rule group.

mutation_protection instance-attribute 

mutation_protection: NotRequired[MutationProtectionStatus]

If enabled, this setting disallows modification or removal of the association, to help prevent against accidentally altering DNS firewall protections. When you create the association, the default setting is DISABLED.

name instance-attribute 

name: Name

A name that lets you identify the association, to manage and use it.

priority instance-attribute 

priority: Priority

The setting that determines the processing order of the rule group among the rule groups that you associate with the specified VPC. DNS Firewall filters VPC traffic starting from the rule group with the lowest numeric priority setting.

You must specify a unique priority for each rule group that you associate with a single VPC. To make it easier to insert rule groups later, leave space between the numbers, for example, use 101, 200, and so on. You can change the priority setting for a rule group association after you create it.

The allowed values for Priority are between 100 and 9900.

tags instance-attribute 

tags: NotRequired[TagList]

A list of the tag keys and values that you want to associate with the rule group association.

vpc_id instance-attribute 

vpc_id: ResourceId

The unique identifier of the VPC that you want to associate with the rule group.