Skip to content

Restrict access to a Dremio instance

Last updated on

By default, a STACKIT Dremio instance accepts connections from any address. With an Access Control List (ACL) you can limit access to a list of IPv4 or IPv6 CIDR ranges, for example your office network or the egress addresses of your applications.

  • The ACL applies to all public endpoints of the instance: the Dremio Console, the Iceberg catalog and Arrow Flight.
  • A client can connect if its address is in the listed ranges. Requests from any other address are rejected with 403 Forbidden before they reach Dremio.
  • An empty ACL allows access from any address.
  • Changes take effect within a few seconds. The instance doesn’t restart.

Enter each range in CIDR notation, for example 203.0.113.0/24 or 2001:db8::/32. To allow a single address, use a /32 prefix for IPv4 or a /128 prefix for IPv6.

You can set the ACL when you create an instance in the Dremio section of the STACKIT Portal, or change it later by editing the instance.

  1. Open the creation wizard for a new instance, or the edit dialog of an existing instance.
  2. In the ACL IP ranges field, enter a CIDR range.
  3. To allow more ranges, click Add IP range and enter the next range.
  4. To remove a range, click the remove icon next to it.
  5. Click Save.

To allow access from any address again, remove all ranges and click Save.

In the STACKIT Dremio API, the ACL is the acl field of a Dremio instance. You can set it when you create an instance or update it later. An update replaces the whole list, so always send all ranges you want to allow:

Terminal window
stackit curl -X PUT -H "Content-Type: application/json" \
--data '{"acl": ["203.0.113.0/24", "198.51.100.17/32"]}' \
https://api.dremio.eu01.stackit.cloud/v1beta/projects/<PROJECT_ID>/regions/eu01/dremios/<DREMIO_ID>

To remove the restriction, send an empty list ({"acl": []}). If an update request doesn’t contain the acl field, the current ACL stays unchanged. If any entry isn’t a valid CIDR range, the API rejects the request with 400 Bad Request and the current ACL stays in place.