SpiceDB Dedicated Configuration
This guide provides information about the configuration options available to you when deploying a SpiceDB Dedicated Permissions System.
Permissions System Type
Please select the choice (Production or Development) that is appropriate for the Permissions System you are deploying. This choice will not effect the performance or security of your Permissions System, but may impact your Permissions System in the future, so please choose appropriately.
Your SpiceDB Dedicated environment can be provisioned with multiple isolated datastores. If you have more than one, choose the datastore that is appropriate for the Permissions System you are deploying.
SpiceDB Dedicated has two update channels:
regular . You can select the update channel when you launch the Permissions System or in the settings page after you’ve launched it.
rapid - gets every release that is not a release candidate.
regular - trails behind
rapid by at least one release.
After you’ve deployed your Permissions System, you can choose to keep up to date with a channel automatically, or you can “pin” to a version by un-checking the automatic updates box. If you uncheck the automatic release box, you’ll still be able to update, but will have to pick the next version manually.
There are two rollout strategies:
rolling update and
rolling updateis a zero downtime strategy for upgrading to a new version. This is recommended for prod Permissions Systems.
immediateinvolves downtime, but is faster than
Single region deployment
If you are deploying a single region Permissions System, define a single cluster.
Define a cluster for every region you want to deploy into.
For production clusters, we recommend selecting the Cluster Class with the largest number of replicas and processing units. For non-production clusters, you can select whatever Cluster Class is appropriate for your workload. If you have questions about your overall utilization or would like to provision a custom Cluster Class, please reach out to your AuthZed account team.