> I just point my code to read/write from/to R2 instead of S3
This is probably worse for CloudFront than for S3 itself.
Double paying for storage is still going to be cheaper than egress fees overall.
This is probably worse for CloudFront than for S3 itself.
Double paying for storage is still going to be cheaper than egress fees overall.
- Set up the S3 mirror into R2
- Migrate your code to read from R2.
- Set up SQS to populate with S3 Create events. SQS listeners just make a GET request to R2 for that file.
- Generate S3 events and populate SQS by running List operations or by abusing S3 Lifecycle Management.
- Let it process.
- Switch writes to R2.
This all assumes you can’t delete from S3 till R2 is fully ready. Depending on the application, you could switch over writes to R2 in a different step and also possibly delete the S3 file in the SQS processor.