You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: app/authzed/guides/setting-up-private-networking/page.mdx
+62-1Lines changed: 62 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,7 +103,68 @@ desc = No schema has been defined; please call WriteSchema to start
103
103
104
104
## GCP Steps
105
105
106
-
Coming Soon
106
+
Most users of AuthZed Dedicated on GCP privately connect to SpiceDB with GCP [Private Service Connect](https://docs.cloud.google.com/vpc/docs/private-service-connect). Private Service Connect enables a private connection from your GCP Project and VPC to SpiceDB. Users of AuthZed Dedicated also have the option to configure SpiceDB to be accessed from the open internet.
| DNS name | This will be provided to you by Authzed |
140
+
| IP address | Enter your Private Service Connect endpoint IP |
141
+
142
+
### Add Permission System
143
+
144
+
1. Login to your SpiceDB management console
145
+
2. On the homepage, select "Add Permission System"
146
+
3. Configure your permission system to your liking and create it
147
+
4. If you enabled [Restricted API Access](../concepts/restricted-api-access), configure it and provision a token. Otherwise, provision a token without FGAM
148
+
149
+
### Verify Connectivity
150
+
151
+
Verify connectivity from client machine with the [Zed CLI tool](https://github.com/authzed/zed)
152
+
153
+
```zed
154
+
zed context set permission_system_name example.com:443 sdbst_h256_123
155
+
```
156
+
157
+
```zed
158
+
zed schema write example.yaml
159
+
```
160
+
161
+
```zed
162
+
zed schema read
163
+
```
164
+
165
+
The last Zed command should display the schema to your terminal.
0 commit comments