跳到正文
实时
Databricks Blog·· 5 天前

Databricks 承诺在欧洲建设三个新区域以满足主权要求

Databricks' Commitment to European Sovereignty

要点速览

Databricks 在欧洲已有十年投资,服务 17 个云区域,新增三个欧洲主权云区域:Azure 意大利、Azure 西班牙和 AWS 欧洲主权云(AWS ESC),满足严格合规和驻留要求,支持欧盟数据边界,客户可自主选择数据存储位置和访问权限。Databricks 将在微软主权公共云和 AWS 欧洲主权云上提供 Azure Databricks 服务,确保欧洲客户数据和生产环境保持欧洲控制。

正文

Over a Decade of Investment in Europe

Databricks has been building in Europe since our first regional launch in the Netherlands in 2017. Today we serve thousands of European enterprises across 17 European cloud regions. Our growing European team of more than 2,000 employees works from 15 offices in Europe, including several engineering hubs. In addition, European customers can now contract directly with a Databricks European Union (EU) entity, making procurement simpler for customers that require a European counterparty.

That investment has always been driven by a specific philosophy: customers should control where their data lives, how it's protected, and who can access it. Our platform is built so customers decide where their data is stored, and who holds the keys that protect it. Databricks is the engine that processes data, not a vault that holds it. Combined with open formats and a multi-cloud architecture, this means sovereignty never has to come at the cost of lock-in. We are extending our partnership by committing to build three new regions in Europe, Azure Italy, Azure Spain and AWS European Sovereign Cloud (AWS ESC).

Building to Meet Sovereign Requirements

Meeting strict compliance and residency requirements isn’t new territory for us. Databricks was an early leader in GDPR readiness and among the first to build functionality such as “right-to-be-forgotten” deletion management. We’ve continued to evolve our platform alongside regulations and customer expectations, including support for the EU Data Boundary, so customer data is stored and processed where customers choose. For highly regulated workloads, Databricks already operates under some of the world’s most rigorous frameworks.

Today, we’re seeing growing interest from European customers in stronger sovereignty controls. To help them continue innovating on Databricks while their data and production environments remain under European control, we’re expanding our sovereign cloud commitments across both Azure and AWS.

Delivering Azure Databricks on Microsoft Sovereign Public Cloud

Microsoft Sovereign Public Cloud brings sovereignty controls to the Azure regions. Databricks and Microsoft are working together to extend those controls to Azure Databricks, including operational oversight, personnel controls, and transparency measures designed to meet the expectations of European regulators and customers. Databricks is classified as a regional service on Azure and has been Azure EU Data Boundary compliant since EUDB launched.

Deploying on AWS European Sovereign Cloud (AWS ESC)

We're committing to making Databricks natively available on the AWS European Sovereign Cloud. AWS ESC is a physically and logically independent cloud, operated within the EU, that AWS brought to general availability in early 2026. It's designed to give European organizations the highest levels of operational autonomy, resilience, and data protection, and it's a natural home for the most demanding sovereignty workloads. Bringing Databricks to AWS ESC means customers won't have to choose between sovereignty and a modern data and AI platform.

Looking Ahead

True digital sovereignty is a journey, not a switch. Our immediate focus is bringing Databricks to the Microsoft Sovereign Public Cloud regions and AWS European Sovereign Cloud, and we’ll keep adding controls that strengthen our sovereign offering over time, including support for any open standard compatible storage so customers can keep data on-premises or in European clouds.

As the sovereign landscape evolves, we’ll keep listening to our customers and partners and evaluating additional sovereign options based on what they need. Our commitment stays the same: customers should control where their data lives, how it’s protected, and who can access it.

Forward-looking statement: This post describes plans and timelines that are subject to change and do not represent a commitment to deliver any specific functionality by a specific date.

来源: Databricks Blog · databricks.com