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.
Obtain all three values from the same unexpired AWS session. The engine does not
renew saved temporary keys. Local secret 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