Stay organized with collections
Save and categorize content based on your preferences.
Developer Connect complies with
data residency requirements. Data residency describes
where your data is stored at rest. To ensure compliance,
Developer Connect does the following:
stores resource data in regional Spanner instances
replicates data only within designated cloud regions
queues webhook data within regional Spanner queues
However, this isn't true for all connections. By default,
GitHub connections use a global
Pub/Sub topic for event delivery. The topic is then replicated to
regional subscriptions. Although the Pub/Sub messages aren't
stored permanently by Pub/Sub, this global routing doesn't meet
data residency requirements because Pub/Sub stores each message
in a global topic temporarily.
When you create a GitHub connection using Google Cloud CLI, that connection is
regional, but the Developer Connect GitHub app that the connection uses is
global, and thefore doesn't comply with data residency requirements.
When you create a GitHub connection using Google Cloud console, data residency is
disabled by default for that connection. You can enable it by activating the
Enable data residency checkbox. Doing so makes this GitHub connection
data-residency compliant. Developer Connect creates a GitHub app for your
connection, owned by your GitHub user account or organization. The app uses a
per-connection, regionalized webhook endpoint.
To create a data-residency compliant GitHub connection, see
Connect to GitHub.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[],[],null,["# About data residency\n\nDeveloper Connect complies with\n[data residency requirements](/terms/data-residency). Data residency describes\nwhere your data is stored *at rest*. To ensure compliance,\nDeveloper Connect does the following:\n\n- stores resource data in regional Spanner instances\n- replicates data only within designated cloud regions\n- queues webhook data within regional Spanner queues\n\nHowever, this isn't true for all connections. By default,\n[GitHub connections](/developer-connect/docs/connect-github-repo) use a global\nPub/Sub topic for event delivery. The topic is then replicated to\nregional subscriptions. Although the Pub/Sub messages aren't\nstored permanently by Pub/Sub, this global routing doesn't meet\ndata residency requirements because Pub/Sub stores each message\nin a global topic temporarily.\n\nWhen you create a GitHub connection using Google Cloud CLI, that connection is\nregional, but the Developer Connect GitHub app that the connection uses is\nglobal, and thefore doesn't comply with data residency requirements.\n\nWhen you create a GitHub connection using Google Cloud console, data residency is\ndisabled by default for that connection. You can enable it by activating the\n**Enable data residency** checkbox. Doing so makes this GitHub connection\ndata-residency compliant. Developer Connect creates a GitHub app for your\nconnection, owned by your GitHub user account or organization. The app uses a\nper-connection, regionalized webhook endpoint.\n\nTo create a data-residency compliant GitHub connection, see\n[Connect to GitHub](/developer-connect/docs/connect-github-repo#connection)."]]
