Snowflake Regions

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 geographical 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 accounts. If you wish to use Snowflake across multiple regions, you must have a separate Snowflake account in each region and the data in these accounts cannot currently be directly accessed or shared between them.

In this Topic:

List of Regions (by Cloud Platform)

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

Cloud Platform Snowflake Region
AWS US West
AWS US East
AWS EU (Dublin)
AWS EU (Frankfurt)
AWS Asia Pacific (Sydney)
   
Microsoft Azure East US 2
Microsoft Azure West Europe

Snowflake features and services are identical across regions; however, there are some differences in unit costs for credits and data storage. 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 your account type, see the pricing page (in the Snowflake website).

Account Names and Regions

Snowflake account hostnames have the following structure:

<account_name>.snowflakecomputing.com

Where <account_name> is the name of your account (provided by Snowflake).

However, depending on where your account is hosted, <account_name> must also include region and cloud platform segments, as shown in the following table:

Cloud Platform Snowflake Region Account Name Format Examples
AWS US West only <account_name> xy12345
AWS All other AWS regions <account_name>.<region> xy12345.us-east-1 . xy12345.eu-central-1
       
Azure All regions <account_name>.<region>.<platform> xy12345.east-us-2.azure . xy12345.west-europe.azure

For example, for an account named xy12345:

If the account is in: Your full hostname would be:
AWS US West xy12345.snowflakecomputing.com
AWS US East xy12345.us-east-1.snowflakecomputing.com
Azure East US 2 xy12345.east-us-2.azure.snowflakecomputing.com

Important

VPS (Virtual Private Snowflake) accounts, as well as accounts with AWS PrivateLink enabled, do not utilize the hostname structure described above. For more details:

United States (US) Regions

Snowflake maintains the following US regions on the AWS and Azure cloud platforms:

Cloud Platform Snowflake Region Geographic Location Standard Edition Support Hours
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 geographical proximity to your end users.

European Union (EU) Regions

Snowflake maintains two EU regions on the AWS cloud platform:

Cloud Platform Snowflake Region Geographic Location Standard Edition Support Hours
AWS EU (Dublin) Ireland 6:00am - 6:00pm Central Europe Time (CEST or CEDT)
AWS EU (Frankfurt) Germany 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 the EU (Dublin) Region or EU (Frankfurt) 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 geographical 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 Regions

Snowflake currently maintains a single Asia Pacific region on the AWS cloud platform:

Cloud Platform Snowflake Region Geographic Location Standard Edition Support Hours
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 AP (Sydney) will be maintained in this region only, unless explicitly copied or moved by users.