Google Cloud Storage
Dette indhold er ikke tilgængeligt i dit sprog endnu.
Connect a Google Cloud Storage bucket to Agent Context. Agent Context reads structured files from your bucket and makes them queryable with SQL. Each file becomes a table.
- Go to Agent Context in the dashboard
- Click Add Source → Google Cloud Storage
- Enter your HMAC credentials and the GCS path to the file
- Click Test Connection to verify, then Save
Connection Parameters
Section titled “Connection Parameters”| Parameter | Required | Description |
|---|---|---|
| Access Key | No | GCS HMAC access key |
| Secret Key | No | GCS HMAC secret key |
| GCS URI | Yes | Path to the file: bucket/path/to/file.parquet |
| File Format | No | Auto-detected from extension. Override: csv, tsv, parquet, json, jsonl |
Alternatively, you can paste a connection string with all parameters.
Getting HMAC Keys
Section titled “Getting HMAC Keys”GCS uses HMAC keys (S3-compatible) for authentication:
- Go to Google Cloud Console → Cloud Storage → Settings → Interoperability
- Under Service account HMAC, click Create a key
- Copy the Access key and Secret key
The service account needs roles/storage.objectViewer on the bucket.
Supported File Formats
Section titled “Supported File Formats”| Format | Extension | Notes |
|---|---|---|
| Parquet | .parquet | Columnar format. Best performance for large datasets. |
| CSV | .csv | Auto-detects delimiter, headers, and column types. |
| TSV | .tsv | Tab-separated values. |
| JSON | .json | JSON array format. |
| JSONL | .jsonl | Newline-delimited JSON. One record per line. |
Troubleshooting
Section titled “Troubleshooting”| Issue | Fix |
|---|---|
| Access denied | Verify the HMAC key is valid and the service account has roles/storage.objectViewer on the bucket. |
| No tables found | Check that the GCS URI points to a supported file format. |
| Invalid credentials | Ensure the HMAC key hasn’t been revoked. Regenerate in Cloud Console → Interoperability. |