Deployed 0140ca8 to 12.0 with MkDocs 1.6.1 and mike 2.1.3

12.0/setup/migrate_backends_data/index.html

@@ -1051,6 +1051,21 @@
     </span>
   </a>
 
+    <nav class="md-nav" aria-label="Create a new temporary seafile.conf">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#migrating-to-sse-c-encrypted-s3-storage" class="md-nav__link">
+    <span class="md-ellipsis">
+      Migrating to SSE-C Encrypted S3 Storage
+    </span>
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
 </li>
 
         <li class="md-nav__item">
@@ -4227,6 +4242,21 @@
     </span>
   </a>
 
+    <nav class="md-nav" aria-label="Create a new temporary seafile.conf">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#migrating-to-sse-c-encrypted-s3-storage" class="md-nav__link">
+    <span class="md-ellipsis">
+      Migrating to SSE-C Encrypted S3 Storage
+    </span>
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
 </li>
 
         <li class="md-nav__item">
@@ -4348,6 +4378,43 @@ <h2 id="create-a-new-temporary-seafileconf">Create a new temporary seafile.conf<
 mv seafile.conf /opt
 </code></pre></div>
 <p>Repalce the configurations with your own choice.</p>
+<h3 id="migrating-to-sse-c-encrypted-s3-storage">Migrating to SSE-C Encrypted S3 Storage<a class="headerlink" href="#migrating-to-sse-c-encrypted-s3-storage" title="Permanent link">&para;</a></h3>
+<p>If you are migrating to S3 storage, and want your data to be encrypted at rest, you can configure SSE-C encryption options in the temporary seafile.conf. Note that you have to use Seafile Pro 11 or newer and make sure your S3 storage supports SSE-C.</p>
+<div class="highlight"><pre><span></span><code>cat &gt; seafile.conf &lt;&lt; EOF
+[commit_object_backend]
+name = s3
+bucket = seacomm
+key_id = ******
+key = ******
+use_v4_signature = true
+use_https = true
+sse_c_key = XiqMSf3x5ja4LRibBbV0sVntVpdHXl3P
+
+[fs_object_backend]
+name = s3
+bucket = seafs
+key_id = ******
+key = ******
+use_v4_signature = true
+use_https = true
+sse_c_key = XiqMSf3x5ja4LRibBbV0sVntVpdHXl3P
+
+[block_backend]
+name = s3
+bucket = seablk
+key_id = ******
+key = ******
+use_v4_signature = true
+use_https = true
+sse_c_key = XiqMSf3x5ja4LRibBbV0sVntVpdHXl3P
+EOF
+
+mv seafile.conf /opt
+</code></pre></div>
+<p><code>sse_c_key</code> is a string of 32 characters.</p>
+<p>You can generate <code>sse_c_key</code> with the following command：</p>
+<div class="highlight"><pre><span></span><code>openssl rand -base64 24
+</code></pre></div>
 <h2 id="migrating-large-number-of-objects">Migrating large number of objects<a class="headerlink" href="#migrating-large-number-of-objects" title="Permanent link">&para;</a></h2>
 <p>If you have millions of objects in the storage (especially fs objects), it may take quite long time to migrate all objects. More than half of the time is spent on checking whether an object exists in the destination storage. <strong>Since Pro edition 7.0.8</strong>, a feature is added to speed-up the checking.</p>
 <p>Before running the migration script, please set this env variable:</p>

12.0/setup/setup_with_amazon_s3/index.html

@@ -4436,7 +4436,11 @@ <h3 id="use-server-side-encryption-with-customer-provided-keys-sse-c">Use server
 use_https = true
 sse_c_key = XiqMSf3x5ja4LRibBbV0sVntVpdHXl3P
 </code></pre></div>
-<p><code>ssk_c_key</code> is a 32-byte random string.</p>
+<p><code>sse_c_key</code> is a string of 32 characters.</p>
+<p>You can generate <code>sse_c_key</code> with the following command：</p>
+<div class="highlight"><pre><span></span><code>openssl rand -base64 24
+</code></pre></div>
+<p><strong>Important</strong>: 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 <a href="migrate_backends_data/#migrating-to-sse-c-encrypted-s3-storage">storage backend migration documentation</a>.</p>
 <h2 id="other-public-hosted-s3-storage">Other Public Hosted S3 Storage<a class="headerlink" href="#other-public-hosted-s3-storage" title="Permanent link">&para;</a></h2>
 <p>There are other S3-compatible cloud storage providers in the market, such as Blackblaze and Wasabi. Configuration for those providers are just a bit different from AWS. We don't assure the following configuration works for all providers. If you have problems please contact our support</p>
 <div class="highlight"><pre><span></span><code>[commit_object_backend]