File Storage
Sentry provides an abstraction called ‘filestore’ which is used for storing files (such as release artifacts).
The default backend stores files on the local disk in /tmp/sentry-files which is not suitable for production use.
filestore.backend: "filesystem"
filestore.options:
location: "/tmp/sentry-files"
In addition to the configuration below, you’ll need to make sure the shell environment has the variable GOOGLE_APPLICATION_CREDENTIALS set. For more information, refer to the Google Cloud documentation for setting up authentication.
filestore.backend: "gcs"
filestore.options:
bucket_name: "..."
The S3 storage backend supports authentication either by using an access key or by IAM instance roles. When using the latter, omit access_key and secret_key. By default, S3 objects are created with the public-read ACL which means that the account/role used must have the PutObjectAcl permission in addition to PutObject, along with GetObject and DeleteObject. If you don't want your uploaded files to be publically-accessible you can set default_acl to private.
filestore.backend: "s3"
filestore.options:
access_key: "..."
secret_key: "..."
bucket_name: "..."
default_acl: "..."
filestore.backend: "s3"
filestore.options:
access_key: "..."
secret_key: "..."
bucket_name: "..."
endpoint_url: "https://minio.example.org/"
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").