Security-conscious enterprises that use cloud SaaS applications need to restrict access to their own employees. Authentication helps to prove user identity, but that does not enforce network location of the users. Accessing a cloud service from an unsecured network can pose security risks to an enterprise, especially when the user may have authorized access to sensitive or personal data. Enterprise network perimeters apply security policies and limit access to external services (for example, firewalls, proxies, DLP, and logging), so access beyond these controls are assumed to be untrusted. Please see IP Access List for full feature documentation.
resource "databricks_workspace_conf" "this" {
custom_config = {
"enableIpAccessLists" = true
}
}
resource "databricks_ip_access_list" "allowed-list" {
label = "allow_in"
list_type = "ALLOW"
ip_addresses = [
"1.1.1.1",
"1.2.3.0/24",
"1.2.5.0/24"
]
depends_on = [databricks_workspace_conf.this]
}
The following arguments are supported:
list_type
- Can only be "ALLOW" or "BLOCK".ip_addresses
- A string list of IP addresses and CIDR ranges.label
- This is the display name for the given IP ACL List.enabled
- (Optional) Boolean true
or false
indicating whether this list should be active. Defaults to true
In addition to all arguments above, the following attributes are exported:
id
- Canonical unique identifier for the IP Access List, same as list_id
.list_id
- Canonical unique identifier for the IP Access List.The databricks_ip_access_list can be imported using id:
terraform import databricks_ip_access_list.this <list-id>
The following resources are often used in the same context: