Skip to main content
How-to guideApplies to: Unified engine deployments
Log in to Polaris with OAuth, then read its S3 table files using an assumed AWS role. The catalog selects separate named credentials for auth and storage.

Prepare both access paths

Use an existing Polaris catalog with a retail warehouse and the SF1 item table in namespace tpcds_sf1. Replace the example URLs, client ID, warehouse, namespace, and Region with your values. The Polaris client needs access to the warehouse and table. These examples request PRINCIPAL_ROLE:ALL; use the scope granted to your client. The table’s data must be in S3. Configure an EKS Pod Identity for the credential-service host and an existing target role as described in Assume an AWS role. The target role needs list/read access to the table’s actual metadata, data, and delete-file prefixes, plus KMS access when needed. Replace the sample role ARN and client secret. No catalog-vended S3 credentials are required for this recipe.

Define the two identities

Attach each credential to its role

s3.region is a catalog option used to open the table’s S3 files. The role ARN and session name are credential options used to acquire AWS credentials. auth selects OAuth for metadata requests; storage selects the AWS role for file reads. An explicit storage reference takes priority over vended credentials. When finished:
Last modified on November 4, 2026