Regions let your organization choose where your data is geographically stored across your regional, national, and international operations.Regions also determine where your compute resources are provisioned.
Snowflake supports regions across all of the Snowflake-supported cloud platforms, grouped intothree global geographic segments (North/South America, Europe/Middle East, and Asia Pacific).
Important
Each Snowflake account is hosted in a single region. If you wish to use Snowflake across multiple regions, you must maintain a Snowflakeaccount in each of the desired regions.
North & South America¶
These regions are supported for organizations that prefer or require their data to be stored in the US, Canada, or Brazil. Multiple regions areprovided to allow your organization to meet its individual compliance requirements for general purpose use. Additional US regions are providedfor organizations that must comply with US government regulations.
Commercial Regions¶
Snowflake supports the following regions in North America (US and Canada) and South America (Brazil) for general commercial use:
CloudPlatform | CloudRegion | CloudRegionID[1] | AdditionalNotes |
|---|---|---|---|
Amazon Web Services (AWS) | |||
USWest(Oregon) | us-west-2 | ||
USEast(Ohio) | us-east-2 | ||
USEast(N. Virginia) | us-east-1 | ||
Canada(Central) | ca-central-1 | ||
SouthAmerica(Sao Paulo) | sa-east-1 | ||
GoogleCloudPlatform(GCP) | |||
USCentral1(Iowa) | us-central1 | ||
USEast4(N. Virginia) | us-east4 | ||
Microsoft Azure | |||
WestUS2(Washington) | westus2 | ||
CentralUS(Iowa) | centralus | ||
SouthCentralUS(Texas) | southcentralus | ||
EastUS2(Virginia) | eastus2 | ||
CanadaCentral(Toronto) | canadacentral | ||
[1] The map preceding this table displays the cloud-specific IDs for the supported regions.
U.S. Regions Supporting Public Sector Workloads¶
Snowflake makes the following regions available to customers that require compliance with common U.S. Federal and state governmentstandards. These regions are only supported for Snowflake accounts on Business Critical Edition(or higher).
Note
If your Snowflake account is in a U.S. government region and you want to access data products that areoffered privately or on the Snowflake Marketplace, or offer listings either privately or on the Snowflake Marketplace, you must review andacknowledge a cross-region disclaimer for your organization.
For details, see:
Prepare to provide listings from accounts in U.S. government regions
Prepare to access listings from accounts in U.S. government regions
Limitations for accessing listings from accounts in U.S. government regions
- U.S. Commercial Regions
The following commercial regions meet the requirements for Snowflake’s compliance with the U.S. government standards set forth in thetable below. By uploading workloads covered by the below compliance standards, customers agree toSnowflake’s U.S. Government Commercial Compliance Addendum.
Cloud Region
Cloud Region ID
Compliance standards
Amazon Web Services
US East 1 (Commercial Gov - N. Virginia)
us-east-1
FedRAMP (Moderate)
StateRAMP (Moderate)
TX-RAMP (Level 2)
FIPS 140-2
US East 1 (Commercial - N. Virginia)
us-east-1
TX-RAMP (Level 2, Provisional)
Microsoft Azure
South Central US (Texas)
southcentralus
TX-RAMP (Level 2)
- U.S. SnowGov Regions
Snowflake makes the following SnowGov Regions on AWS GovCloud (US) (us-gov-west-1) and Microsoft Azure Government (usgovvirginia)available to customers who require additional security designed for US government regulated workloads and other types of sensitive data.These regions are operated by Snowflake personnel who are U.S. persons located within the U.S. Certain features that are available inSnowflake’s commercial regions may not be available or may be different in its SnowGov Regions. Use of and access to Snowflake in any ofthe SnowGov Regions are limited solely to U.S. Government Customers or U.S. Government Contractors (unless otherwise agreed upon bySnowflake in its sole discretion) and are subject to Snowflake’s U.S. SnowGov Region Terms of Service. As used here, a“U.S. Government Customer” means a Snowflake customer that is: (a) a U.S. Federal, state, or local government entity or (b) a tribalgovernment entity; and a “U.S. Government Contractor” means a commercial entity that is required to process data provided by a U.S.Government Customer to perform a prime contract or subcontract with or for such entity.
The SnowGov Regions support U.S. government standards, such as FedRAMP, DoD Impact Levels, StateRAMP, TX-RAMP, FIPS-140-2, and theInternational Traffic in Arms Regulations (ITAR) by default. As noted in the table below, certain standards require the customer toaccept supplemental contract terms. You must contact Snowflake and agree to the supplemental terms before uploading workloads covered bythese standards.
Self-provisioning of initial Snowflake accounts is not available in the SnowGov Regions. To provision an initial account in these regions,you must contact Snowflake.
Cloud Region
Cloud Region ID
Workloads Supported by Default
Workloads Requiring Supplemental Contract Terms
Amazon Web Services
US Gov West 1 (FedRAMP High Plus)
us-gov-west-1
FedRAMP (High) Department of Defense (DoD) Impact Level 4 (IL4)
StateRAMP (High)
TX-RAMP (Level 2)
FIPS 140-2
NIST 800-171
ITAR
DFARS 252.204-7012
DFARS 252.239-7010
The Department of Justice (DoJ) Criminal Justice Information Systems (CJIS) Security Policy
IRS Publication 1075
US Gov West 1 (DoD)
us-gov-west-1
DoD IL4
BCAP
FIPS 140-2
NIST 800-171
ITAR
DFARS 252.204-7012
DFARS 252.239-7010
DoJ CJIS Security Policy
IRS Publication 1075
US Gov East 1 (FedRAMP High Plus)
us-gov-east-1
FedRAMP (High)
DoD IL4
StateRAMP (High)
TX-RAMP (Level 2)
FIPS 140-2
NIST 800-171
ITAR
DFARS 252.204-7012
DFARS 252.239-7010
DoJ CJIS Security Policy
IRS Publication 1075
Microsoft Azure Government
US Gov Virginia
usgovvirginia
FedRAMP (Moderate)
StateRAMP (Moderate)
TX-RAMP (Level 2)
FIPS 140-2
NIST 800-171
ITAR
DFARS 252.204-7012
DOJ CJIS Security Policy
IRS Publication 1075
Note that the government regions of the cloud providers do not allow event notifications to be sent to or from other commercial regions. For more information, see AWS GovCloud (US) and Azure Government.
Europe & Middle East¶
These regions are supported for organizations that prefer or require their data to be stored in the European Union (EU), UnitedKingdom (UK), or Middle East. Multiple regions are provided to allow your organization to meet its individual compliance and datasovereignty requirements.
Snowflake supports the following European and Middle East regions:
CloudPlatform | CloudRegion | CloudRegionID[1] | AdditionalNotes |
|---|---|---|---|
Amazon Web Services (AWS) | |||
EU(Ireland) | eu-west-1 | ||
Europe(London) | eu-west-2 | ||
EU(Paris) | eu-west-3 | ||
EU(Frankfurt) | eu-central-1 | ||
EU(Zurich) | eu-central-2 | ||
EU(Stockholm) | eu-north-1 | ||
Google Cloud Platform (GCP) | |||
EuropeWest2(London) | europe-west2 | ||
EuropeWest4(Netherlands) | europe-west4 | ||
Microsoft Azure | |||
UKSouth(London) | uksouth | ||
NorthEurope(Ireland) | northeurope | ||
WestEurope(Netherlands) | westeurope | ||
SwitzerlandNorth(Zurich) | switzerlandnorth | ||
UAENorth(Dubai) | uaenorth | ||
[1] The map preceding this table displays each supported region and corresponding cloud-specific ID.
Asia Pacific & China¶
These regions are supported for organizations that prefer or require their data to be stored in Japan, Korea, India, Southeast Asia,Australia, and China. Multiple regions are provided to allow your organization to meet its individual compliance and data sovereigntyrequirements.
Snowflake supports the following Asia Pacific and China regions:
CloudPlatform | CloudRegion | CloudRegionID[1] | AdditionalNotes |
|---|---|---|---|
Amazon Web Services (AWS) | |||
Asia Pacific(Tokyo) | ap-northeast-1 | ||
Asia Pacific(Osaka) | ap-northeast-3 | ||
Asia Pacific(Seoul) | ap-northeast-2 | ||
Asia Pacific(Mumbai) | ap-south-1 | ||
Asia Pacific(Singapore) | ap-southeast-1 | ||
Asia Pacific(Sydney) | ap-southeast-2 | This region can be used by government agencies that require compliance with Australianprivacy and security standards, such as IRAP (Protected). | |
Asia Pacific(Jakarta) | ap-southeast-3 | ||
China(Ningxia) —Preview, coming soon | cn-northwest-1 | The China region is not available yet. A preview of the China region isscheduled for an upcoming release. The China region is separate from other Snowflake regions and is wholly operated byDigital China Cloud Technology Limited (DCC), an authorized operating partner ofSnowflake, Inc. Customers who wish to create and use Snowflake accounts in theChina region must sign a separate agreement with DCC in accordance with allapplicable rules and regulations. Customers with existing Snowflake accounts will not be able to access resourcesin the China region, and vice versa. Some features may not be available in the Chinaregion. | |
Microsoft Azure | |||
CentralIndia(Pune) | centralindia | ||
JapanEast(Tokyo) | japaneast | ||
SoutheastAsia(Singapore) | southeastasia | ||
Australia East(New South Wales) | australiaeast | This region can be used by government agencies that require compliance with Australianprivacy and security standards, such as IRAP (Protected). | |
[1] The map preceding this table displays each supported region and corresponding cloud-specific ID.
Region Time Zones for Support¶
Snowflake supports multiple editions with each edition offering different levels of service.
Effective May 1, 2020:
All new accounts, regardless of Snowflake Edition, receive Premier support, which includes 24/7 coverage.
Standard Edition accounts that were provisioned before this date will continue to receive Standard support until the accounts aretransitioned to Premier support.
Standard support hours are Monday - Friday, 6:00 AM - 6:00 PM, across all regions, but the time zones vary depending on the geographiclocation of the region:
- North America:
Pacific Time (PST or PDT)
- Europe & Middle East:
Central Europe Time (CET or CEST)
- Asia Pacific:
Australian Eastern Time (AEST or AEDT)
Differences Between Regions¶
Snowflake features and services are identical across regions except for some newly-introduced features (based on cloud platform or region).However, there are some differences in unit costs for credits and data storage between regions.
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 thepricing page (on the Snowflake website).
Viewing a List of Regions Available for an Organization¶
A organization administrator (i.e. user with the ORGADMIN role) can view a list of regions available for an organization through Snowsight or using SQL:
- Snowsight:
Select Admin » Accounts » Create New Account » Choose Your Region.
- SQL:
Execute the SHOW REGIONS command.
Considerations for Choosing a Region for Your Account¶
When you request a Snowflake account, either through self-service or a Snowflake representative, you can choose the region where theaccount is located. For example, you can decide to locate an account in a particular region on a particular cloud platform to addresslatency concerns and/or provide additional backup and disaster recovery beyond the standard recovery support provided by Snowflake.Snowflake does not place any restrictions on the region where you choose to locate each account.
If latency is a concern, you should choose the available region with the closest geographic proximity to your end users; however, this mayhave cost implications, due to pricing differences between the regions. For more details, see thepricing page (on the Snowflake website).
If you are a government agency or a commercial organization that must comply with specific privacy and security requirements of the USgovernment, you can choose between two dedicated government regions provided by Snowflake.
Important
Regions do not limit user access to Snowflake; they only dictate the geographic location where data is stored and compute resources areprovisioned.
In addition, Snowflake does not move data between accounts, so any data in an account in a region remains in the region unless usersexplicitly choose to copy, move, or replicate the data.
Specifying Region Information in Your Account Hostname¶
A hostname for a Snowflake account starts with an account identifier and ends with the Snowflake domain(snowflakecomputing.com). Snowflake supports two formats to use as theaccount identifier in your hostname:
Account name (preferred)
Account locator
Important
If you choose the account locator as your account identifier, you may need to include additional segments in the locator thatspecify the cloud region and cloud platform where your account is hosted.
For more details, see Format 2: Account locator in a region.
