Backups to two different S3 regions no longer work

제품 지원
1

Today we have updated Discourse to latest commit, and S3 backup system stopped working

When accessing to /admin/backups, an error failed message is raised, and the JSON outputs this:
The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint

Just before updating, it was working correctly
Now we can’t either make new backups or view current ones

We also use media uploads to S3, which is working properly at this moment
The media bucket is “kodular-community”, and it’s hosted in Dublin

However, the backups bucket is called “kodular-community-backups” and it’s hosted in Oregon

Maybe this issue could be releated in some way to the fact that it’s trying to fetch the “kodular-community-backups” from Dublin endpoint, as it’s the region it’s specified in Admin (?)

But I don’t know why it was working before and suddenly after updating it stopped working

2

I don’t think using different regions for backups and uploads is a supported configuration. If it ever worked it was a bug.

3

Yes, it was a bug that I fixed two days ago. Both buckets must be in the same region.

4

But how was that a bug? What was the effect of it?
Everything was working properly before :confused:

5

The bug was that the s3_region setting was completely ignored. That prevented Discourse from creating a new bucket and I think other things like uploading/downloading backups from the browser should have failed as well when the bucket’s region differed from the s3_region setting.

6

It doesn’t make any sense for them to be geographically separate.

8

백업 버킷을 다른 리전에 두는 옵션을 제공하는 것이 실제로 좋은 아이디어일 것 같습니다. @gerhard 님, 이 기능을 추가하는 것이 얼마나 어려울까요? 기본값은 에셋과 동일하게 설정하되, 값이 지정된 경우 이를 오버라이드하도록 하면 됩니다.

사이트가 us-east-1[1]에 호스팅되어 있고 해당 리전에 장애가 발생하더라도, 다른 리전에서 백업을 가져와 사이트를 다른 곳에 재구성할 수 있습니다.

  1. 사이트를 그곳에 호스팅하지 마세요. 최악의 리전입니다. ↩︎