Boomi is a Snowflake Elite partner, and this update makes that partnership tangible: the Boomi Integration Snowflake connector now supports the High security policy setting on every Boomi-hosted Runtime Cloud — including, for the first time, Dedicated Cloud Service. No infrastructure to provision, no security exception to justify.

Closing the Runtime Cloud Gap

A Runtime Cloud runs on shared infrastructure, executing processes that belong to more than one account. That’s why every Runtime Cloud enforces a security policy — the setting that governs what a runtime can reach outside its own account directory, keeping one tenant’s processes out of another’s files and network. Boomi hosts three types of Runtime Clouds: Public Cloud Service, Dedicated Cloud Service, and Managed Cloud Service. And customers can also self-host their own if they prefer. High is the strictest security policy Boomi offers, and whether it’s configurable depends on which Runtime Cloud you’re on.

Until now, the Snowflake connector supported only MCS and customer-hosted Runtime Clouds. With this release, it also connects to PCS and DCS both of which run exclusively under the High security policy setting.

What’s Different Now

The Snowflake connector now runs under the High security policy setting. Three things follow:

• PCS and DCS are now supported for Snowflake integrations — the fully managed, multi-tenant path is open for the first time.
• On MCS, the security policy stays at High. No need to lower it to accommodate the connector.
• On customer-hosted Runtime Clouds, teams that dropped to Low for Snowflake can return to High and keep the workload where it is.

What This Unlocks

• Data warehouse sync at enterprise scale. Load and query Snowflake from ERP, CRM, and finance systems on a Boomi-hosted cloud.
• Regulated industries on cloud-native integration. Financial services and healthcare teams can build Snowflake pipelines on PCS or DCS and stay inside their internal security review requirements.
• Faster onboarding for new Snowflake use cases. No need to step up to a managed offering, or stand up a customer-hosted Runtime Cloud, just to support Snowflake use cases — teams can start building on a Boomi-hosted Runtime Cloud immediately.

Why It Matters

Security posture and deployment flexibility shouldn’t be in conflict. This feature release gives customers more freedom in how they deploy and manage Runtime Cloud environments. Previously, customers had to self-host or shelve Snowflake integration projects due to deployment constraints.

Getting Started

No migration is required. Existing Snowflake integrations continue to run as-is. Customers on MCS or a customer-hosted Runtime Cloud who dropped their security policy to Low to accommodate the connector can now raise it back to High. New projects can start directly on PCS or DCS.

Ready to take your Boomi and Snowflake integrations to the next level? Get started quickly with our pre-built Boomi Marketplace solution templates.

Full details are in the Snowflake connector documentation.