Or you could write some of your own tooling in a Worker, etc.

But if you're looking for something to just work super easy out of the box, then I'd recommend following this channel and waiting until things are a little more generally available, and less private-beta-y.

The stock s3 tools seem to work as long as you limit the concurrency to 2 or 3

Or don’t use multipart

I would try when it's in beta It's super hard to setup but it's fine

John has a pretty good doc going then about what works well with different things: https://gist.github.com/johnspurlock-skymethod/6027c81953f81aa535d889d86a1061ba I'd start there 🙂

I got aws cli installed Reminder to myself /home/container/r2-cli/v2/2.6.1/bin/aws

Yeah the AWS CLI works the best, but you need to tame it as beelzabub mentioned and John documented quite a bit in that gist.

How to set it up

Did you follow John's info? https://gist.github.com/johnspurlock-skymethod/6027c81953f81aa535d889d86a1061ba#aws-cli-official-amazon-cli. Where did you get stuck?

It needs the auth info provided every command

R2 is still in beta so a lot of things still require experimenting for yourself and playing with it until it works, we can only help so much.

Any alternative?

You could play with other S3 compatible tooling, but you're really not going to find anything that "just works" right now unfortunately. If you're open to tinkering, there's a lot of info in that doc and this channel which will allow you to get things up and running, but as @Erisa | Support Engineer said, it's going to take some experimentation on your end all the time things are in private beta and documentation and tooling is still being updated.

John's guide doesn't told me how to auth first

So I can't even use it

Hmm I saw a s3 style config at the section before it

Is it the config?

@James don't need to sha256 token right?

Hey Darren, please don't ping people.

We've warned you about it before, and as James said, you need to either figure it out from the docs or wait until the tooling is improved for R2.

Ok

You need to sha256 it in EVERY case that is using the S3 API right now.

You can make a file called

~/.aws/credentials

and set

[default]
aws_access_key_id = apikeyid
aws_secret_access_key = secretwithsha256

You still need all of the other arguments, but this allows you to skip the credential ones.

Can I save it anywhere else

No

Seems like maybe it is customizable using environment variables? https://docs.aws.amazon.com/sdkref/latest/guide/file-location.html

Probably useful if you are accessing multiple providers and need to pick which config to use

Ah right yeah I forgot about that

Is token id changed every token reroll