IMPORTANT: Developer documentation for the current main branch. This content is unreleased and may change before the next Polaris release. For stable user documentation, see the latest release docs.

Creating a catalog on S3 compatible cloud providers

Several S3 compatible storage providers can be configured as backends for your Polaris catalog. Refer to child pages under this documentation section for some of the possible options.

For the polaris catalogs create command there are a few s3-only options:

--storage-type s3
--role-arn  (Only for AWS S3) A role ARN to use when connecting to S3
--current-kms-key  (Deprecated; only for AWS S3) Use --encryption-key instead
--allowed-kms-key  (Deprecated; only for AWS S3) Use --encryption-key instead
--encryption-key   (Only for AWS S3) AWS KMS key identifier(s) that this catalog and its clients may use to encrypt S3 data; these keys are also granted decryption permissions (zero or more)
--decryption-key  (Only for AWS S3) AWS KMS key identifier(s) that this catalog and its clients may use to decrypt S3 data (zero or more)
--no-sts  (Only for S3) Indicates that Polaris should not use STS (e.g. if STS is not available)
--region  (Only for S3) The region to use when connecting to S3
--external-id  (Only for S3) The external ID to use when connecting to S3