In a support discussion titled “S3 region vs. Discourse region,” dandv reports that forum backups fail due to a mismatch between the S3 bucket’s region and the region configured in Discourse’s Files setting. dandv questions why Discourse uses technical region names (e.g., ap-northeast-1, us-gov-west-1) instead of AWS’s human-readable ones (e.g., Tokyo, Ireland), and asks if Discourse could auto-create backup buckets to avoid manual region configuration. zogstrip clarifies that Discourse needs the region to communicate with or create S3 buckets, and that S3 always requires a region (defaulting to US East if unspecified). In response to dandv, zogstrip confirms the Discourse region must match the S3 bucket’s region and acknowledges the naming confusion, promising to improve localization. Later, zogstrip announces that S3 region names in Discourse are now localized to match AWS’s display names, improving clarity for users as implemented here.
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?
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