Snowflake Regions

Related Topics

Snowflake Regions let your organization choose where your data is geographically stored across your global operations. They also determine where your compute resources are provisioned. You can choose to have multiple accounts in separate regions to address global latency concerns and/or provide additional backup and disaster recovery support beyond the standard support provided by Snowflake.

Note that regions do not limit user access to Snowflake; they only dictate the geographic location where data is stored and compute resources are provisioned.

Important

Each Snowflake account is located in a single region (i.e. multi-region accounts are not supported).

In addition, Snowflake does not yet support accessing or sharing data between regions. If you wish to use Snowflake across multiple regions, you must have a separate Snowflake account in each region.

In this Topic:

List of Regions (by Cloud Platform)

Snowflake maintains the following regions (with more planned for the future):

Snowflake Region Region ID Notes
AWS US West us-west-2 This is the default region; it is not utilized/required unless AWS PrivateLink is enabled for your account.
AWS US East us-east-1  
AWS EU (Dublin) eu-west-1  
AWS EU (Frankfurt) eu-central-1  
AWS Asia Pacific (Sydney) ap-southeast-2  
     
Azure East US 2 east-us-2.azure  
Azure West Europe west-europe.azure  

Note

Snowflake features and services are identical across regions; however, there are some differences in unit costs for credits and data storage. In addition to region, another factor that impacts unit costs is whether your Snowflake account is On Demand or Capacity.

For more information about pricing as it pertains to a specific region and account type, see the pricing page (in the Snowflake website).

Region and Cloud Platform in Account Names

A hostname for a Snowflake account starts with a unique account name (provided by Snowflake) and ends with snowflakecomputing.com.

However, depending on the cloud platform (AWS or Azure) and Snowflake Region where your account is hosted, the full account name may require additional segments, as shown in the following diagram:

Structure of Snowflake account hostnames

For example, for an account named xy12345:

If the account is in: Full account name is:
AWS US West xy12345
AWS US East xy12345.us-east-1
AWS EU (Frankfurt) xy12345.eu-central-1
AWS EU (Dublin) xy12345.eu-west-1
AWS AP (Sydney) xy12345.ap-southeast-2
   
Azure East US 2 xy12345.east-us-2.azure
Azure West Europe xy12345.west-europe.azure

Important

The structure of your account name is different if either of the following are true:

United States (US) Regions

Snowflake maintains the following US regions:

Cloud Platform Snowflake Region Geographic Location Support Hours for Standard Edition
AWS US West Oregon 6:00am - 6:00pm Pacific Time (PST or PDT)
AWS US East Virginia 6:00am - 6:00pm Pacific Time (PST or PDT)
       
Azure East US 2 Virginia 6:00am - 6:00pm Pacific Time (PST or PDT)

If your account is hosted on AWS and latency is a concern, you should choose the available US region with the closest geographic proximity to your end users.

European Union (EU) Regions

Snowflake maintains the following EU regions:

Cloud Platform Snowflake Region Geographic Location Support Hours for Standard Edition
AWS EU (Frankfurt) Germany 6:00am - 6:00pm Central Europe Time (CEST or CEDT)
AWS EU (Dublin) Ireland 6:00am - 6:00pm Central Europe Time (CEST or CEDT)
       
Azure West Europe Netherlands 6:00am - 6:00pm Central Europe Time (CEST or CEDT)

These regions are provided for organizations that prefer or require their data to be stored in the European Union. Multiple regions are provided to allow organizations to meet their individual compliance and data sovereignty requirements. Snowflake does not move data between accounts, so any data in an account in an EU region will be maintained in this region only, unless explicitly copied or moved by users.

If latency is a concern, you should choose the available EU region with the closest geographic proximity to your end users; however, this may have cost implications, due to pricing differences between the regions. For more details, see the pricing page (in the Snowflake website).

Asia Pacific (AP) Regions

Snowflake currently maintains a single AP region:

Cloud Platform Snowflake Region Geographic Location Support Hours for Standard Edition
AWS AP (Sydney) Australia 6:00am - 6:00pm Australian Eastern Time (AEST or AEDT)

This region is provided for organizations that prefer or require their data to be stored in the Asia Pacific part of the world. Snowflake does not move data between accounts, so any data in an account in an AP region will be maintained in this region only, unless explicitly copied or moved by users.