✏️ Fix CORSRules content typo for S3 config

baptisteArno · Nov 1, 2023 · 585e1d4 · 585e1d4
1 parent b80bea1
commit 585e1d4
Showing 1 changed file with 7 additions and 7 deletions.
diff --git a/apps/docs/docs/self-hosting/guides/s3.md b/apps/docs/docs/self-hosting/guides/s3.md
@@ -21,16 +21,16 @@ To function properly, your S3 bucket must have the following configuration:
   {
     "CORSRules": [
       {
-        "AllowedOrigins": ["*"],
-        "AllowedMethods": ["GET"],
         "AllowedHeaders": ["*"],
-        "MaxAgeSeconds": 3000
+        "AllowedMethods": ["PUT", "POST"],
+        "AllowedOrigins": ["*"],
+        "ExposeHeaders": ["ETag"]
       }
     ]
   }
   ```
 
-- Access policy:
+- Access policy (replace `<bucket-name>` with the name of your S3 bucket):
   ```json
   {
     "Version": "2012-10-17",
@@ -60,10 +60,10 @@ Some S3 providers like AWS provide a user interface that allows you to directly
    {
      "CORSRules": [
        {
-         "AllowedOrigins": ["*"],
-         "AllowedMethods": ["GET"],
          "AllowedHeaders": ["*"],
-         "MaxAgeSeconds": 3000
+         "AllowedMethods": ["PUT", "POST"],
+         "AllowedOrigins": ["*"],
+         "ExposeHeaders": ["ETag"]
        }
      ]
    }