S3 region vs. Discourse region


(Dan Dascalescu) #1

My forum’s backups don’t work due to a mismatch between the region of the S3 bucket specified on Amazon’s site, and the region specified in the Discourse Files setting.

Another user had the same problem:

What exactly does the Discourse region setting do, since the S3 bucket already has a region assigned to it when you create it?

Also,

Maybe the Discourse region setting is used when creating S3 buckets automagically?

Would it be possible to automagically create the backup bucket as well, and avoid having to mess with region settings?


(Régis Hanol) #2

We need to know the region the bucket was created in otherwise we won’t be able to “talk to it”.

The Discourse region setting is used to know which region of S3 to use. Be it to talk to an existing bucket or to create a new one.

S3 requires a region (if you don’t specify one, it will default to US East)


(Dan Dascalescu) #3

Does the Discourse region need to be set to the same region as that of the S3 buckets?

What is the mapping between S3 regions, and Discourse regions? Could Discourse simply use the same set of names that S3 uses, i.e.

US Standard
Oregon
Northern California
Ireland
Singapore
Tokyo
Sydney
Sao Paulo
Frankfurt
Seoul

Discourse has ap-northeast-1, ap-southeast-1, ap-southeast-2, us-gov-west-1 right now, which to me at least, is unnecessarily confusing. I actually can’t fathom what us-gov-west-1 might correspond to, or whether Ireland and Frankfurt are both eu-west-1 or something else. Am I missing something here? Is there a good reason for using those names instead of the S3 city/region names?

Here’s another user wondering why these are named differently.


(Régis Hanol) #4

Yes.

The names used in Discourse are the “technical” names. They used to show these instead of City/Country. I will make sure they’re properly translated so they better match those displayed by AWS :wink:


(Régis Hanol) #5

There you go @dandv. S3 region names are now localized :evergreen_tree: