How-to guideApplies to: Unified engine deployments
Exchange a runtime token file for an AWS role and read a Parquet dataset.
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.
Configure the role web-identity trust for the token issuer and audience. Mount a
valid subject-token file in the credential-service runtime. The target role
needs access to the S3 data.
Values to collect
- Role ARN, token-file path, AWS region, bucket, prefix, and S3 endpoint.
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 dataset rows. This checks the token exchange, role
trust, and S3 access together.
Clean up
Remove the view and credential; leave the external role and token source in
place.
Last modified on November 4, 2026