From 89be4ac7f34bb829ace40b71d82e7bde3090c30f Mon Sep 17 00:00:00 2001 From: Jiaqiang Xu Date: Tue, 5 Nov 2024 11:45:29 +0800 Subject: [PATCH] Update setup_with_amazon_s3.md Fix link to migrate backend data. --- manual/setup/setup_with_amazon_s3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manual/setup/setup_with_amazon_s3.md b/manual/setup/setup_with_amazon_s3.md index 0a4509edf..799ee29bf 100644 --- a/manual/setup/setup_with_amazon_s3.md +++ b/manual/setup/setup_with_amazon_s3.md @@ -107,7 +107,7 @@ You can generate `sse_c_key` with the following command： openssl rand -base64 24 ``` -**Important**: If you have existing data in your S3 storage bucket, turning on the above configuration will make your data inaccessible. That's because Seafile server doesn't support encrypted and non-encrypted objects mixed in the same bucket. You have to create a new bucket, and migrate your data to it by following [storage backend migration documentation](migrate_backends_data/#migrating-to-sse-c-encrypted-s3-storage). +!!! note "If you have existing data in your S3 storage bucket, turning on the above configuration will make your data inaccessible. That's because Seafile server doesn't support encrypted and non-encrypted objects mixed in the same bucket. You have to create a new bucket, and migrate your data to it by following [storage backend migration documentation](./migrate_backends_data.md#migrating-to-sse-c-encrypted-s3-storage)." ## Other Public Hosted S3 Storage