# S3 region vs. Discourse region

**URL:** https://meta.discourse.org/t/s3-region-vs-discourse-region/38067
**Category:** Support
**Created:** [1월 17, 2016, 5:03오전 UTC](https://meta.discourse.org/t/s3-region-vs-discourse-region/38067 "2016-01-17T05:03:20Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![dandv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dandv/32/169779_2.png) [@dandv](https://meta.discourse.org/u/dandv)
#### Post date: [1월 17, 2016, 5:03오전 UTC](https://meta.discourse.org/t/s3-region-vs-discourse-region/38067/1 "2016-01-17T05:03:20Z")

</div>

My [forum’s backups don’t work due to a mismatch between the region](https://meta.discourse.org/t/configure-automatic-backups-for-discourse/14855/42) of the S3 bucket specified on Amazon’s site, and the region specified in the Discourse Files setting.

Another user had the same problem:

[https://meta.discourse.org/t/backups-not-uploading-to-s3/19707/8?u=dandv](https://meta.discourse.org/t/backups-not-uploading-to-s3/19707/8)

What exactly does the Discourse region setting do, since [the S3 bucket already has a region assigned to it when you create it](https://meta.discourse.org/t/setting-up-file-and-image-uploads-to-s3/7229/53)?

Also,

> [@Set up file and image uploads to S3](https://meta.discourse.org/t/set-up-file-and-image-uploads-to-s3/7229/1):
>
> Note how you did not have to create your S3 bucket? That’s because Discourse will automagically create it for you if it doesn’t already exists. 😉

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?

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [1월 17, 2016, 6:07오후 UTC](https://meta.discourse.org/t/s3-region-vs-discourse-region/38067/2 "2016-01-17T18:07:33Z")

</div>

> [@dandv](#):
>
> What exactly does the Discourse region setting do, since the S3 bucket already has a region assigned to it when you create it?

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

> [@dandv](#):
>
> Maybe the Discourse region setting is used when creating S3 buckets automatigically?

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.

> [@dandv](#):
>
> Would it be possible to automagically create the backup bucket as well, and avoid having to mess with region settings?

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

---

<div class="post-metadata">

### Author: ![dandv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dandv/32/169779_2.png) [@dandv](https://meta.discourse.org/u/dandv)
#### Post date: [1월 19, 2016, 2:45오전 UTC](https://meta.discourse.org/t/s3-region-vs-discourse-region/38067/3 "2016-01-19T02:45:37Z")

</div>

> [@zogstrip](#):
>
> 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.

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](https://meta.discourse.org/t/s3-backups-to-eu-west-1-ireland-failing/17309).

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [1월 19, 2016, 8:13오전 UTC](https://meta.discourse.org/t/s3-region-vs-discourse-region/38067/4 "2016-01-19T08:13:21Z")

</div>

> [@dandv](#):
>
> Does the Discourse region need to be set to the same region as that of the S3 buckets?

Yes.

> [@dandv](#):
>
> Could Discourse simply use the same set of names that S3 uses, i.e.

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 😉

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [1월 19, 2016, 4:15오후 UTC](https://meta.discourse.org/t/s3-region-vs-discourse-region/38067/5 "2016-01-19T16:15:43Z")

</div>

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

[https://github.com/discourse/discourse/commit/11ea16a91ad0179b55d4ded2081e0beda699c93e](https://github.com/discourse/discourse/commit/11ea16a91ad0179b55d4ded2081e0beda699c93e)

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [4월 18, 2019, 8:16오후 UTC](https://meta.discourse.org/t/s3-region-vs-discourse-region/38067/7 "2019-04-18T20:16:58Z")

</div>



---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [4월 23, 2019, 8:08오전 UTC](https://meta.discourse.org/t/s3-region-vs-discourse-region/38067/8 "2019-04-23T08:08:53Z")

</div>


