docs: clarify data region backup table#3276
Open
ofeliacode wants to merge 1 commit into
Open
Conversation
|
Someone is attempting to deploy a commit to the langfuse Team on Vercel. A member of the Team first needs to authorize it. |
ofeliacode
force-pushed
the
docs-clarify-data-region-backups
branch
from
July 14, 2026 19:27
3824f90 to
4fe7a26
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Follow-up to #2844.
Clarifies the Cross-Region Backup table by labeling the secondary AWS regions with the same EU / US / JP mapping used for the
primary regions.
Also fixes
Clickhouse->ClickHousecasing in the Data Regions page.Greptile Summary
This PR clarifies the Cross-Region Backup table in the Data Regions security page and fixes a casing typo.
Clickhouseis corrected toClickHousein the opening paragraph.Confidence Score: 5/5
This is a purely editorial documentation update with no code, logic, or configuration changes.
Both changes are accurate and self-consistent: secondary region labels mirror the primary region labels exactly (EU → eu-central-1, US / HIPAA → us-east-2, JP → ap-northeast-3), and the ClickHouse casing correction matches the product's official branding. Nothing about the underlying backup architecture or region assignments was altered.
No files require special attention.
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD subgraph EU["EU Region"] EU_P["Postgres\neu-west-1"] EU_CH["ClickHouse\neu-west-1"] EU_S3["S3 Media\neu-west-1"] end subgraph US["US / HIPAA Region"] US_P["Postgres\nus-west-2"] US_CH["ClickHouse\nus-west-2"] US_S3["S3 Media\nus-west-2"] end subgraph JP["JP Region"] JP_P["Postgres\nap-northeast-1"] JP_CH["ClickHouse\nap-northeast-1"] JP_S3["S3 Media\nap-northeast-1"] end subgraph Secondary["Secondary Regions (Disaster Recovery)"] EU_SEC["EU: eu-central-1"] US_SEC["US / HIPAA: us-east-2"] JP_SEC["JP: ap-northeast-3"] end EU_P -- "AWS Backup daily snapshot copy\nre-encrypted with CMK\n7-day retention" --> EU_SEC US_P -- "AWS Backup daily snapshot copy\nre-encrypted with CMK\n7-day retention" --> US_SEC JP_P -- "AWS Backup daily snapshot copy\nre-encrypted with CMK\n7-day retention" --> JP_SEC EU_CH -. "Not replicated" .-> EU_SEC EU_S3 -. "Not replicated" .-> EU_SEC%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%% flowchart TD subgraph EU["EU Region"] EU_P["Postgres\neu-west-1"] EU_CH["ClickHouse\neu-west-1"] EU_S3["S3 Media\neu-west-1"] end subgraph US["US / HIPAA Region"] US_P["Postgres\nus-west-2"] US_CH["ClickHouse\nus-west-2"] US_S3["S3 Media\nus-west-2"] end subgraph JP["JP Region"] JP_P["Postgres\nap-northeast-1"] JP_CH["ClickHouse\nap-northeast-1"] JP_S3["S3 Media\nap-northeast-1"] end subgraph Secondary["Secondary Regions (Disaster Recovery)"] EU_SEC["EU: eu-central-1"] US_SEC["US / HIPAA: us-east-2"] JP_SEC["JP: ap-northeast-3"] end EU_P -- "AWS Backup daily snapshot copy\nre-encrypted with CMK\n7-day retention" --> EU_SEC US_P -- "AWS Backup daily snapshot copy\nre-encrypted with CMK\n7-day retention" --> US_SEC JP_P -- "AWS Backup daily snapshot copy\nre-encrypted with CMK\n7-day retention" --> JP_SEC EU_CH -. "Not replicated" .-> EU_SEC EU_S3 -. "Not replicated" .-> EU_SECReviews (1): Last reviewed commit: "docs: clarify data region backup table" | Re-trigger Greptile