During the night, dark mode.

oh

Thanks for bringing it up. This is a known issue. We're already looking into it on ourside.

If I remember to switch, that is

Aww... sad kitten makes me sad 😢

Also do cats cry? Not sure... never seen one actually do it.

Also #812577823599755274

I'm getting errors when Authenticating with the s3 api

so I created the token and tested it out

but when I tried the s3 endpoint

I get not authorized

I tried the AWS way of doing it (at least what I though it was)

The S3 endpoint uses Sigv4 which isn't what you're trying. Also, you have to do sha256 of the token to get the

secret_access_key

. The

access_id

you get from the network pane of the browser dev tools. There's several threads about this earlier.

We'll try and get some docs up on configuring SigV4 soon.

Lol

We also have GraphQL analytics you can play with now. Some example queries: R2Storage

query GetR2Storage($accountTag: string, $dateStart: string, $dateEnd: string) {
  viewer {
    accounts(filter: {accountTag: $accountTag}) {
      r2StorageAdaptiveGroups(
        limit: 100,
        orderBy:[
          bucketName_DESC
        ],
        filter: {
          date_geq: $dateStart,
          date_leq: $dateEnd
        }) {
        max {
          payloadSize,
          objectCount
        }
        dimensions{
          date,
          bucketName
        }
      }
    }
  }

R2Operations

query GetR2Operations($accountTag: string, $dateStart: string, $dateEnd: string) {
  viewer {
    accounts(filter: {accountTag: $accountTag}) {
      r2OperationsAdaptiveGroups(
        limit: 100,
        orderBy:[
          actionType_DESC
        ],
        filter: {
          date_geq: $dateStart,
          date_leq: $dateEnd
        }) {
        sum {
          requests
        }
        dimensions{
          date,
          actionType
        }
      }
    }
  }
}

Oh

nice

thx

👀 👀 👀 awesome! just updated my unofficial schema pages with these new datasets (available in all plans!) https://pages.johnspurlock.com/graphql-schema-docs/cloudflare.html

anyone get presigned urls to work yet? https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html

Wondering if they are implemented, didn't see it on the r2 s3 compat doc either way...

Presigned URLs aren't implemented yet. We have it on the roadmap. What's your use-case?

ah ok - redirecting from a non-cloudflare server directly to presigned GETs

Yeah. Unfortunately for now you'd have to front that with your own worker that has the relevant bucket(s) bound in.

ok, looking forward to see this in a future release - very common with content hosting companies using s3 - and this would give them a drop in replacement without first having to go through the workers learning process