Network Rules¶

Supported Network Identifiers¶

Administrators need to be able to restrict access based on the network identifier associated with the origin or destination of a request. Network rules allow administrators to allow or block the following network identifiers:

Incoming requests

• IPv4 addresses

• VPCE IDs of AWS VPC endpoints . VPC IDs are not supported.

• LinkIDs of Azure private endpoints. Execute the SYSTEM$GET_PRIVATELINK_AUTHORIZED_ENDPOINTS function to retrieve the LinkID associated with an account.

Outgoing requests

Domains, including an optional port range

Each network rule contains a list of one or more network identifiers of the same type. The network rule’s TYPE property indicates the type of identifiers that are included in the rule. For example, if the TYPE property is IPV4, then the network rule’s value list must contain valid IPv4 addresses or address ranges in CIDR notation.

Incoming vs. Outgoing Requests¶

The mode of a network rule indicates whether the Snowflake feature that uses the rule restricts incoming or outgoing requests.

Creating a Network Rule¶

An administrator executes the CREATE NETWORK RULE command to create a new network rule, specifying a list of network identifiers along with the type of those identifiers.

The administrator uses the MODE parameter to indicate whether the network rule is used to restrict incoming or outgoing requests. If the administrator does not include the MODE parameter, it defaults to INGRESS, which means the network rule is used by network policies to restrict incoming network traffic to the Snowflake service.

Creating a network rule does not define whether it is allowing or blocking the network identifiers. Administrators specify those restrictions when configuring the Snowflake feature that uses the network rule.

Example: Network rule for network policy

Code in the following example uses a custom role to create a network rule that can be used to allow or block traffic from a range of IP addresses to the Snowflake service:

CREATE ROLE network_admin;
GRANT USAGE ON DATABASE securitydb TO ROLE network_admin;
GRANT USAGE ON SCHEMA securitydb.myrules TO ROLE network_admin;
GRANT CREATE NETWORK RULE ON SCHEMA securitydb.myrules TO ROLE network_admin;
USE ROLE network_admin;

CREATE NETWORK RULE cloud_network
  MODE = INGRESS
  TYPE = IPV4
  VALUE_LIST = ('47.88.25.32/27');

Modifying a Network Rule¶

The owner of a network rule can execute the ALTER NETWORK RULE command to replace the rule’s network identifiers and comment. You cannot add or remove individual network identifiers to the network rule; existing identifiers are lost when adding new values.

The TYPE and MODE of the network rule cannot be modified.

For example, the owner of a network rule can modify it so it can be used to allow or block traffic from a new range of IPv4 addresses:

ALTER NETWORK RULE cloud_network SET VALUE_LIST = ('47.88.25.32/27');

The owner of the network rule could also remove all network identifiers from the rule:

ALTER NETWORK RULE cloud_network UNSET VALUE_LIST;

Replication of Network Rules¶

Network rules are schema-level objects and are replicated with the database in which they are contained.

For information about replicating the network policies that use network rules, see Replicating Network Policies.

Privileges and Commands¶