How-to guideApplies to: Unified engine deployments
Use an explicit saved AWS key set for one Parquet file source.
Before you start
Use an existing nonempty Parquet dataset and a configured S3 file-source root
covering its prefix. A credential does not authorize an arbitrary storage root.
The identity needs list/read access to the bucket and actual files, plus KMS
decrypt permission when needed. Use the region and HTTPS endpoint for that
bucket. Keep the temporary view and its SELECT in the same Workbench workspace.
Use a reachable MinIO S3 endpoint, keys accepted by that server, and its
configured region. Use HTTPS when available. For an explicitly configured
HTTP-only local MinIO instance, change allow_http to true. The input root must
point at this MinIO service.
Saved key values require the encrypted secret store.
Values to collect
- Input bucket/prefix, endpoint, region, and matching key values.
Run the SQL
Replace every <placeholder> before running. Use unused names for the resources
below. Run the statements in order in Workbench.
Check the result
The SELECT should return rows from the chosen dataset. For temporary AWS keys,
it also verifies the matching session token.
Clean up
Remove only the local view, credential, and secrets.
Last modified on November 4, 2026