Data Sharing and Snowflake Marketplace · Topic 2 of 10
Cross-Region and Cross-Cloud Sharing, Replication and Auto-Fulfillment
Share across regions and clouds with replication or Cross-Cloud Auto-Fulfillment, including refresh options, costs, limits and cross-cloud data governance.
- 6 min
- Includes a diagram
- Cross region and cross cloud sharing always needs a copy in the consumer region.
- Auto fulfillment is the least effort for listings; manual replication gives control.
- Refresh: trigger, interval (one minute to eight days) or schedule; interval and schedule do not combine.
What it is
A direct share reaches only accounts in the same region on the same cloud. A consumer in another region or on another cloud needs the data to exist in its own region first. There are two ways to get it there: replication, which the provider sets up and pays for, and Cross-Cloud Auto-Fulfillment, where Snowflake does the copying for a listing.
Both create a copy in the other region. The consumer still sees live looking, read only data, but it is only as fresh as the last refresh.
How it works
Cross-region sharing with replication
The manual route uses database replication to place a copy in an account in the target region, then shares from that account.
-- provider account
ALTER DATABASE sales ENABLE REPLICATION TO ACCOUNTS myorg.region_b_acct;
-- region B account
CREATE DATABASE sales AS REPLICA OF myorg.prod_acct.sales;
ALTER DATABASE sales REFRESH;
-- then create a share in region B and add the consumer
Costs and limits to know:
- The replica is a real copy, so the provider pays storage for it in each region.
- Refreshes use serverless compute and cross region transfer, and both are billed.
- Consumers see changes only after a refresh, which can be scheduled.
- Replication sets the freshness of the data. It does not move the share itself; a new share in the target region is still needed.
- Database and share replication work on all editions.
The role of replication
Replication is the mechanism behind every cross region share. The only question is who runs it.
| Approach | Who replicates | Best for |
|---|---|---|
| Manual database replication | Provider, with its own secondary accounts | Full control, a few regions, internal use |
| Cross-Cloud Auto-Fulfillment | Snowflake, behind a listing | Private and public listings to many regions, least administration |
Cross-Cloud Auto-Fulfillment
For a listing, the provider turns on auto fulfillment and Snowflake replicates the data product to each region where a consumer asks for it. It manages a secure share area in each region.
- Timing: For a private listing, fulfillment starts after the chosen consumers get the listing. For a public listing, it starts after a consumer in that region gets it.
- First fulfillment into a new region transfers the whole data product. Later ones refresh it. Several listings on the same database fulfill it once per region.
- Refresh options: trigger based (on demand with
SYSTEM$TRIGGER_LISTING_REFRESH), interval based (from one minute to eight days) or schedule based. Interval and schedule based refresh cannot be used together. - Cost: The provider pays for the extra storage, transfer and refresh compute. The cost depends on the size of the data product.
- Limits: A full account is needed (not a trial). The default size limit is 10 TB, which an account administrator can raise through
LISTING_AUTO_FULFILLMENT_INITIAL_REFRESH_SIZE_LIMIT_IN_TB. Accounts that signed up through a cloud provider's marketplace can fulfill only within that cloud. - Failures: A refresh failure summary is emailed daily to the listing contact address.
- Required for: application packages and paid listings. Private listings to other regions use it automatically and cannot be replicated by hand.
- Monitoring:
LISTING_AUTO_FULFILLMENT_REFRESH_DAILYandLISTING_AUTO_FULFILLMENT_DATABASE_STORAGE_DAILYinSNOWFLAKE.DATA_SHARING_USAGEshow refreshes and the storage used.
| Scope option | Meaning |
|---|---|
SUB_DATABASE (default) | Object level fulfillment |
SUB_DATABASE_WITH_REFERENCE_USAGE | Account level scheduling for application packages |
FULL_DATABASE | Deprecated |
"Share with customers in other regions and clouds, least administrative effort" means a listing with Cross-Cloud Auto-Fulfillment. "Provider wants direct control of the replica" means manual replication.
Cross-Cloud Data Governance
Data is copied to another region, so its protection has to travel with it. Auto fulfillment scope is the database, schema and table level, not the account level.
- Account level masking policies set on tags are not considered during auto fulfillment. Do not rely on them to protect a listing.
- Share secure views for rows and columns that must stay hidden, as for any share. Do not use
CURRENT_USERorCURRENT_ROLEin them; useCURRENT_ACCOUNT(). - Tri-Secret Secure for the secure share areas must be enabled through Snowflake Support. Results are then encrypted with provider, Snowflake and consumer keys, and each key gives its owner independent control.
- Business Critical accounts use the same secure share area and can apply Business Critical security features.
- Virtual Private Snowflake and government regions are isolated and have their own share areas, so data stays within that environment.
| Control | Cross cloud behavior |
|---|---|
| Secure views | Work as in a normal share |
| Tag based account masking | Not considered by auto fulfillment |
| Tri-Secret Secure | Needs Snowflake Support to enable |
| Residency | Data is copied only to regions where consumers take the listing |
The provider is responsible for deciding which regions may hold the data. Auto fulfillment copies to any region where a consumer gets the listing, so check residency rules before publishing.
Common mistakes
Direct share to another region. It cannot work.
Forgetting storage and transfer costs. Each extra region adds a billed copy.
Using tag based account masking to guard a listing. It is not considered during auto fulfillment.
Replicating a database and expecting the share to follow. A new share is still needed in the target region.
Ignoring the size limit. Over 10 TB needs the limit raised.
What to remember for the exam
- Cross region and cross cloud sharing always needs a copy in the consumer region.
- Auto fulfillment is the least effort for listings; manual replication gives control.
- Refresh: trigger, interval (one minute to eight days) or schedule; interval and schedule do not combine.
- Provider pays storage, transfer and compute; trial accounts are not eligible.
- Secure views and
CURRENT_ACCOUNT()carry governance; Tri-Secret Secure for the share areas goes through Support.
Check yourself
A consumer on another cloud needs the data; the provider wants the least effort. What is used?
A listing with Cross-Cloud Auto-Fulfillment.
What controls how fresh the data is in the other region?
The refresh: on demand, an interval or a schedule.
Which governance feature is not considered by auto fulfillment?
Account level masking policies set on tags.
Topic 2 of 10 in Data Sharing and Snowflake Marketplace
Test yourself on Data Sharing and Snowflake Marketplace
The full Snowflake ADA-C02 question bank has 814 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.