@@ -84,7 +84,9 @@ that you'll need to set up persistent storage on whatever cloud hosting platform
8484you choose to run the Docker container on (e.g. AWS EBS). By default the
8585database is stored locally in SQLite but you may also point it to a SQL database
8686either locally or on a cloud service of your choice following
87- [ these instructions] ( #running-the-database-on-postgres-or-mysql ) .
87+ [ these instructions] ( #running-the-database-on-postgres-or-mysql ) . You can also
88+ configure the backend to use S3 storage for exports, snapshots, modules, files,
89+ and search indexes following [ these instructions] ( #using-s3-storage ) .
8890
8991You should now be able to use the self-hosted backend. Read on for alternative
9092hosting options for production workloads.
@@ -253,6 +255,24 @@ export MYSQL_URL=mysql://<your-username>:<your-password>@aws.connect.psdb.cloud
253255docker compose up
254256```
255257
258+ ## Using S3 Storage
259+
260+ To run the backend with S3 storage, set up the following buckets and environment
261+ variables.
262+
263+ ``` sh
264+ export AWS_REGION=" your-region"
265+ export AWS_ACCESS_KEY_ID=" your-access-key-id"
266+ export AWS_SECRET_ACCESS_KEY=" your-secret-access-key"
267+ export S3_STORAGE_EXPORTS_BUCKET=" convex-snapshot-exports"
268+ export S3_STORAGE_SNAPSHOT_IMPORTS_BUCKET=" convex-snapshot-imports"
269+ export S3_STORAGE_MODULES_BUCKET=" convex-modules"
270+ export S3_STORAGE_FILES_BUCKET=" convex-user-files"
271+ export S3_STORAGE_SEARCH_BUCKET=" convex-search-indexes"
272+ ```
273+
274+ Then run the backend!
275+
256276## Optional configurations
257277
258278- The cloud-hosted product automatically redacts logs to prevent any leaking of
0 commit comments