---
#
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.  See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership.  The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.  You may obtain a copy of the License at
#
#   http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied.  See the License for the
# specific language governing permissions and limitations
# under the License.
#
title: Creating a catalog on S3 compatible cloud providers
linkTitle: S3
type: docs
weight: 100
---

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]({{% ref "../../../command-line-interface#create" %}})
there are a few s3-only options:

```text
--storage-type s3
--role-arn  (Only for AWS S3) A role ARN to use when connecting to S3
--current-kms-key  (Only for AWS S3) The AWS KMS key ARN to be used for encrypting new S3 data
--allowed-kms-key  (Only for AWS S3) AWS KMS key ARN(s) that this catalog and its clients are allowed to use for reading 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
```
