Update cloud-storage.md

[raphaellaude]

Hit this snag re: formatting of cors.json file going through the docs! TY!

[bdon]

Where are you inputting the value with CORSRules as a key? The formatting should be as-is for setting CORS through the S3 Bucket Permissions UI (screenshot)

[raphaellaude]

Ah, all makes sense. I was doing it with the aws s3api CLI:

$ aws s3api put-bucket-cors --bucket pluto-hist --cors-configuration file://cors.json


Error parsing parameter '--cors-configuration': Invalid JSON:
[
    {
        "AllowedHeaders": ["Range"],
        "AllowedMethods": ["GET","HEAD"],
        "AllowedOrigins": ["http://localhost:5173/"],
        "ExposeHeaders": ["ETag"]
    }
]

Where this worked:

$ cat cors.json
{
  "CORSRules": [
    {
        "AllowedHeaders": ["Range"],
        "AllowedMethods": ["GET","HEAD"],
        "AllowedOrigins": ["http://localhost:5173/"],
        "ExposeHeaders": ["ETag"]
    }
  ]
}
$ aws s3api put-bucket-cors --bucket pluto-hist --cors-configuration file://cors.json

I can add a note explaining the two different approaches.

[bdon]

Thanks!