use region other than us-central1 for Google Cloud Functions

Question

From what I can tell, Google Cloud Functions is only available in us-central1, as the drop-down for selecting a region only allows me to select us-central1, and when I try writing my own deploy script using something different for the region option like us-east4, the deploy fails. Is this the case? Is there some hidden way to enable creating a cloud function in us-east4 or some other region?

update: the linked question clarifies this for Firebase but I would love to see an official answer for Cloud Functions in general. My guess based on what I've found online is that until Cloud Functions is out of beta, it will only be available in us-central1.

Answer 1

To view the full list of regions available for Cloud Functions, visit this link:

https://cloud.google.com/functions/docs/locations

Current available regions (June, 2020) are:

Tier 1 pricing

• us-central1 (Iowa)
• us-east1 (South Carolina)
• us-east4 (Northern Virginia)
• europe-west1 (Belgium)
• europe-west2 (London)
• asia-east2 (Hong Kong)
• asia-northeast1 (Tokyo)

Tier 2 pricing

• europe-west3 (Frankfurt)
• europe-west6 (Zurich)
• us-west3 (Salt Lake City)

Answer 2

(Updated July 2018) Good news! Cloud Functions is now available in 4 different regions: Iowa (us-central1), South Carolina (us-east1), Tokyo (asia-northeast1), and Belgium (europe-west1).

To specify your region, you can specify --region during deploy, e.g.

$ gcloud functions deploy howdy --trigger-http --region=europe-west1