# כיצד לנקות את נקודת הקצה של S3 בעת מעבר מדלי GCP ל-AWS S3?

**URL:** <https://meta.discourse.org/t/how-to-clear-s3-endpoint-when-moving-from-gcp-bucket-to-aws-s3/188308>\
**Category:** Product Support\
**Created:** [27 באפריל,‏ 2021,‏ 9:36pm UTC](https://meta.discourse.org/t/how-to-clear-s3-endpoint-when-moving-from-gcp-bucket-to-aws-s3/188308 "2021-04-27T21:36:33Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [27 באפריל,‏ 2021,‏ 9:36pm UTC](https://meta.discourse.org/t/how-to-clear-s3-endpoint-when-moving-from-gcp-bucket-to-aws-s3/188308/1 "2021-04-27T21:36:33Z")

</div>

I’ve got a site with S3 buckets on GCP, so it has an endpoint set. That endpoint is in the sitesettings in the database somehow, so including `DISCOURSE_S3_ENDPOINT: ""` in the ENV does . . . nothing. Rather than clearing the value so that Discourse will substitute the “right” one, it insists on using the GCP endpoint with the AWS bucket keys and such.

I tried explicitly setting the endpoint to the AWS one, but the one that I guessed wasn’t quite right somehow, so it wouldn’t work (that was weeks ago so I can’t remember the particulars).

My idea now is to remove the ENV variables when I crank up the container, manually change over the settings to the new AWS ones, so THEN I can set the env variables as described here and build a new container. Is there something easier that I’m overlooking?

Is there some way to set a `NULL` environment variable, maybe?

---

_[View the full topic](https://meta.discourse.org/t/how-to-clear-s3-endpoint-when-moving-from-gcp-bucket-to-aws-s3/188308)._
