2
0

✏️ Fix CORSRules content typo for S3 config

This commit is contained in:
Baptiste Arnaud
2023-11-01 13:51:38 +01:00
parent b80bea11b4
commit 585e1d4074

View File

@ -21,16 +21,16 @@ To function properly, your S3 bucket must have the following configuration:
{ {
"CORSRules": [ "CORSRules": [
{ {
"AllowedOrigins": ["*"],
"AllowedMethods": ["GET"],
"AllowedHeaders": ["*"], "AllowedHeaders": ["*"],
"MaxAgeSeconds": 3000 "AllowedMethods": ["PUT", "POST"],
"AllowedOrigins": ["*"],
"ExposeHeaders": ["ETag"]
} }
] ]
} }
``` ```
- Access policy: - Access policy (replace `<bucket-name>` with the name of your S3 bucket):
```json ```json
{ {
"Version": "2012-10-17", "Version": "2012-10-17",
@ -60,10 +60,10 @@ Some S3 providers like AWS provide a user interface that allows you to directly
{ {
"CORSRules": [ "CORSRules": [
{ {
"AllowedOrigins": ["*"],
"AllowedMethods": ["GET"],
"AllowedHeaders": ["*"], "AllowedHeaders": ["*"],
"MaxAgeSeconds": 3000 "AllowedMethods": ["PUT", "POST"],
"AllowedOrigins": ["*"],
"ExposeHeaders": ["ETag"]
} }
] ]
} }