This is just how S3 works, it doesn't really matter unless you plan on creating buckets with the S3
This is just how S3 works, it doesn't really matter unless you plan on creating buckets with the S3 client (which in fairness you can actually do)
access_key and secret_key supposed to equate to in cloudflare?



us-east-1 should work, where is your bucket located?
The hostname is part of a banned domain. This web property cannot be added to Cloudflare at this time. If you are an Enterprise customer, please contact your Customer Success Manager. Otherwise, please email abusereply@cloudflare.com with the name of the web property and a detailed explanation of your association with this web property.It's more then likely related to: https://www.cloudflarestatus.com/incidents/wsjmr28lwxw3 (it thinks your account has unpaid invoices, so it restricts you from adding new sites, adding an r2 custom domain is considered a new site)
access_keysecret_keyus-east-1[
{
"AllowedOrigins": [
"*"
],
"AllowedMethods": [
"GET",
"PUT",
"POST",
"HEAD",
"DELETE"
],
"AllowedHeaders": [
"*"
],
"ExposeHeaders": [],
"MaxAgeSeconds": 3000
}
] const signedUrl = await getSignedUrl(
r2,
new PutObjectCommand({
Bucket: process.env.R2_BUCKET_NAME,
Key: filename,
}),
{ expiresIn: 3600 },
);