You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.
Class: Aws::EC2::NetworkAcl Instance Attribute Summary collapseAny associations between the network ACL and one or more subnets.
One or more entries (rules) in the network ACL.
Indicates whether this is the default network ACL for the VPC.
The ID of the network ACL.
The ID of the AWS account that owns the network ACL.
Any tags assigned to the network ACL.
The ID of the VPC for the network ACL.
Creates an entry (a rule) in a network ACL with the specified rule number.
Deletes the specified network ACL.
Deletes the specified ingress or egress entry (rule) from the specified network ACL.
.
Changes which network ACL a subnet is associated with.
Replaces an entry (rule) in a network ACL.
add_data_attribute, add_identifier, #data, data_attributes, #data_loaded?, identifiers, #load, #wait_until
Methods included from Resources::OperationMethods#add_batch_operation, #add_operation, #batch_operation, #batch_operation_names, #batch_operations, #operation, #operation_names, #operations
Constructor Details #initialize(id, options = {}) ⇒ Object #initialize(options = {}) ⇒ Object Instance Attribute Details #is_default ⇒ BooleanIndicates whether this is the default network ACL for the VPC.
#network_acl_id ⇒ StringThe ID of the network ACL.
#owner_id ⇒ StringThe ID of the AWS account that owns the network ACL.
#tags ⇒ Array<Types::Tag>Any tags assigned to the network ACL.
#vpc_id ⇒ StringThe ID of the VPC for the network ACL.
Instance Method Details #create_entry(options = {}) ⇒ StructCreates an entry (a rule) in a network ACL with the specified rule number. Each network ACL has a set of numbered ingress rules and a separate set of numbered egress rules. When determining whether a packet should be allowed in or out of a subnet associated with the ACL, we process the entries in the ACL according to the rule numbers, in ascending order. Each network ACL has a set of ingress rules and a separate set of egress rules.
We recommend that you leave room between the rule numbers (for example, 100, 110, 120, ...), and not number them one right after the other (for example, 101, 102, 103, ...). This makes it easier to add a rule between existing ones without having to renumber the rules.
After you add an entry, you can't modify it; you must either replace it, or create an entry and delete the old one.
For more information about network ACLs, see Network ACLs in the Amazon Virtual Private Cloud User Guide.
#create_tags(options = {}) ⇒ Array<Tag> #delete(options = {}) ⇒ StructDeletes the specified network ACL. You can't delete the ACL if it's associated with any subnets. You can't delete the default network ACL.
#delete_entry(options = {}) ⇒ StructDeletes the specified ingress or egress entry (rule) from the specified network ACL.
#delete_tags(options = {}) ⇒ Array<Tag> #replace_association(options = {}) ⇒ Types::ReplaceNetworkAclAssociationResultChanges which network ACL a subnet is associated with. By default when you create a subnet, it's automatically associated with the default network ACL. For more information, see Network ACLs in the Amazon Virtual Private Cloud User Guide.
This is an idempotent operation.
#replace_entry(options = {}) ⇒ StructReplaces an entry (rule) in a network ACL. For more information, see Network ACLs in the Amazon Virtual Private Cloud User Guide.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4