They either just copy pasted the message or whatever tool you are using default to that message or something but its not integrated with AWS other than using the same API schema

thats an aws s3 url not an r2 url

ahh. Yeah I got the nuget package for .net S3

and it generates it like that

Amazon.S3

Hey Folks - Not the exact way I wanted to introduce myself, but “hi”. I’m Ricky, and I joined Cloudflare on Monday as a member of the Developer Relations team. I wanted to give you all a quick update on what’s been going on with zone plans and R2. We have tooling that protects our network and the quality of service for our users, but we've found that it wasn't tuned properly for our new developer platform services. Candidly, this tooling was too aggressive, and we’ve put a fix in place now. We recognize as a developer platform, blocking traffic to valid production applications is unacceptable. We know many of you in the community have experienced problems with actions taken that disrupt interactions between your zone plan and R2. We've heard your frustrations and we’ve been too slow to fix it. From our founder Matthew to our networking and infrastructure teams, everyone is focused on solving this problem immediately. We truly apologize for the pain and confusion this tooling has caused. Please stay tuned for additional updates. If any developer in our community encounters this again, which should not happen, please immediately forward to Aly (aly@cloudflare.com) and me (rrobinett@cloudflare.com) and we will take the lead on resolving this for you so you don’t have to navigate any red tape.

Anyone has an update on this? Not having any kind on integrity check is not good... https://community.cloudflare.com/t/does-r2-support-checksum-when-uploading-doesnt-seem-so/488674

Uploading to r2 is changing the creation date of the file. How can I preserve it? Thanks

append date to file name? 🤔

when i upload the file to r2 in Object Details the Date Created is 2023-03-31T06:52:13+05:30. While in local storage its different 28 April 2022 at 11:46 PM.

The object details simply states when it was created/uploaded to R2

to manage when the file was actually created in the universe you can add it to the file name and pull it off of that as chientrm mentioned

you can attach custom metadata if that suits your needs

Thanks, i solved it using rclone with -metadata flag

hello everyone, if I want to cancel r2 storage but my bucket already contains files, how do I cancel the bucket? or can I just delete the bucket?

You have to delete the files in the bucket first. You can do it manually, or with a tool like

rclone

.

oh i see, thank you

I was getting a few Internal Server errors and connection abort errors from R2 workers API, I've added retries, but they are still showing up in my logs. Is there anything I can do?

My cors policy:

[
  {
    "AllowedOrigins": [
      "http://localhost:3001"
    ],
    "AllowedMethods": [
      "GET",
      "PUT",
      "POST"
    ]
  }
]

I'm trying to put with a presign, any idea how I can fix this? Is my cors policy correct?

"AllowedHeaders": [
      "Access-Control-Allow-Origin"
    ]

adding this doesn't work either

Howdy! Im using a worker (bound to my r2 bucket) to handle user uploads to r2. What's the recommended way to limit file size? Do I need to use presigned urls for that, or is there another way?

do I need to enable R2.dev subdomain to test or something?

with localhost

This is my Cors policy

[
  {
    "AllowedOrigins": [
      "http://localhost:3001"
    ],
    "AllowedMethods": [
      "GET",
      "PUT",
      "POST",
      "DELETE"
    ],
    "AllowedHeaders": [
      "Authorization",
      "Access-Control-Allow-Origin",
      "Origin"
    ],
    "ExposeHeaders": [
      "Access-Control-Allow-Origin",
      "Access-Control-Allow-Credentials"
    ]
  }
]

>.<