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
3. If your Enterprise deployment is private, connect through the private network endpoint provided for your deployment. For example, Azure Private Link deployments commonly use a private IP or an internal DNS name as the endpoint.
39
43
40
-
4. In your terminal, check the existence of the remote **Project**. Specify the remote LanceDB **Project**`db` and `region`.
44
+
### Verify authentication
45
+
46
+
4. Check that you can reach the deployment and list tables:
41
47
42
48
```bash
43
-
curl -X GET "https://{db}.{region}.api.lancedb.com/v1/tables" \
49
+
curl -X GET "$LANCEDB_URI/v1/tables" \
44
50
-H "Content-Type: application/json" \
45
-
-H "x-api-key: LANCEDB_API_KEY"
51
+
-H "x-api-key: $LANCEDB_API_KEY" \
52
+
-H "x-lancedb-database: $LANCEDB_DATABASE"
46
53
```
47
54
48
-
5. Now, create a **Table** to store data. Let's call it `words`.
55
+
If your deployment endpoint already includes the database host name, you can omit the `x-lancedb-database` header.
56
+
57
+
5. Create a table to confirm write access. Let's call it `words`.
49
58
50
59
```bash
51
-
curl -X POST "https://embedding-yhs6bg.us-east-1.api.lancedb.com/v1/tables/words" \
0 commit comments