Skip to content

feat(settings): show AWS region on project region card - #89592

Open
posthog[bot] wants to merge 1 commit into
masterfrom
posthog-self-driving/docsdpa-answer-five-eu-dpa-questions-5b745f
Open

feat(settings): show AWS region on project region card#89592
posthog[bot] wants to merge 1 commit into
masterfrom
posthog-self-driving/docsdpa-answer-five-eu-dpa-questions-5b745f

Conversation

@posthog

@posthog posthog Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Problem

  • An EU Cloud customer running a data-processing review needs the AWS region of their data in writing. Support cites the project settings region card as that record.
  • The card printed only EU Cloud (or US Cloud) and never the AWS region, so a pay-as-you-go customer — who gets no Principal Agreement — had no in-product statement that their data sits in eu-central-1.
  • Over 90 days the settings page drew far more views than the docs pages that hold the same answer, so the record support points to was the one that omitted the region.

This PR fixes only the in-product region card, which lives in this repo. The DPA page, subprocessor data, and security-handbook version stamp named in the report live in the posthog.com repo and are out of scope here.

Changes

  • The region card now reads EU Cloud (AWS eu-central-1) and US Cloud (AWS us-east-1), so a customer can copy the AWS region straight from settings.
  • Add CLOUD_AWS_REGIONS, a Region → AWS-region map (lib/constants). DEV maps to null, so the extra text only shows for a known cloud.
  • Mechanical: the card falls back to the old EU Cloud text when no AWS region is known.

How did you test this code?

  • pnpm --filter=@posthog/frontend typescript:check — no errors in the changed files (pre-existing failures are all in the unbuilt @posthog/quill workspace).
  • pnpm --filter=@posthog/frontend fix — lint and format clean.
  • No automated test added: the change is a display string gated on a constant map, and this card has no existing test harness. Not manually rendered in a browser.

Automatic notifications

  • Publish to changelog?

Docs update

None.

🤖 Agent context

Autonomy: Fully autonomous

  • Authored by an agent (Claude Code) from a PostHog self-driving inbox report.
  • The report named five EU DPA gaps; four sit in the posthog.com docs repo. This PR addresses the single symptom in this repo — the region card printing no AWS region — and states that scope in Problem rather than reaching across repos.
  • AWS regions (us-east-1, eu-central-1) are already public in the PostHog docs.

Created with PostHog Desktop from this inbox report.

The project region card printed only "EU Cloud" or "US Cloud" and never
the AWS region. Support cites this card as the written record of where a
customer's data is hosted, so a pay-as-you-go customer had no way to see
"eu-central-1" in the product.

Add a Region to AWS-region map and append the AWS region to the card, so
EU Cloud reads "EU Cloud (AWS eu-central-1)" and US Cloud reads
"US Cloud (AWS us-east-1)".

Generated-By: PostHog Desktop
Task-Id: c750ec55-487f-44f5-8c2f-36a30183a0a2
@posthog

posthog Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

🦔 ReviewHog reviewed this pull request

Nothing worth raising this time, so here's a calming picture instead:

A happy dog on a sunny path

@trunk-io

trunk-io Bot commented Aug 26, 2026

Copy link
Copy Markdown

Merging to master in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

@stamphog stamphog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small, contained display-only change adding a static AWS region lookup to a settings text string; no risky territory touched.

Gate mechanics and policy version
Gate Result
prerequisites all clear
deny-list no deny categories matched
size 12L, 2F substantive — within ceiling
tier T1-agent / T1a-trivial (12L, 2F, single-area, feat)
stamphog 2.0.0b4 .stamphog/policy.yml @ 4b85429 · reviewed head 4b85429

@github-actions

github-actions Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

🤖 CI report

Trunk lane — non-backend lane

This PR is assigned to the non-backend lane. It does not run backend Python tests and may merge in parallel with PRs in other lanes.

⚠️ Bundle size — 🔺 +52 B (+0.0%)

Uncompressed size of every built .js bundle, compared against the base branch.

Total: 68.40 MiB · 🔺 +52 B (+0.0%)

No file changed by more than 1000 B.

Posted automatically by build-bundle-size-report · uncompressed bytes from dist-report

Eager graph — within budget

How much code each root ships on the eager path — downloaded and parsed before the surface is interactive. Measured from the esbuild output chunks (post-tree-shake, static imports only); lazy import() / React.lazy chunks are not counted.

Root Eager (shipped) Δ vs base Budget
entry (logged-out pages, app bootstrap)
src/index.tsx
1.36 MiB · 22 files no change ███░░░░░░░ 30.2% of 4.51 MiB
authenticated shell (every logged-in page)
src/scenes/AuthenticatedShell.tsx
8.77 MiB · 3,236 files 🔺 +56 B (+0.0%) █████████░ 90.3% of 9.71 MiB

🟢 node_modules/monaco-editor/ stays out of src/index.tsx
🟢 src/lib/components/ActivityLog/describers stays out of src/index.tsx
🟢 [object Object] stays out of src/index.tsx
🟢 [object Object] stays out of src/index.tsx
🟢 node_modules/monaco-editor/ stays out of src/scenes/AuthenticatedShell.tsx
🟢 src/lib/components/ActivityLog/describers stays out of src/scenes/AuthenticatedShell.tsx
🟢 [object Object] stays out of src/scenes/AuthenticatedShell.tsx
🟢 [object Object] stays out of src/scenes/AuthenticatedShell.tsx

Largest files eagerly shipped from src/index.tsx
Size File
126.8 KiB ../node_modules/.pnpm/react-dom@18.3.1_react@18.3.1/node_modules/react-dom/cjs/react-dom.production.min.js
24.6 KiB ../node_modules/.pnpm/buffer@6.0.3/node_modules/buffer/index.js
6.3 KiB ../node_modules/.pnpm/react@18.3.1/node_modules/react/cjs/react.production.min.js
4.5 KiB ../node_modules/.pnpm/@jspm+core@2.1.0/node_modules/@jspm/core/nodelibs/browser/process.js
3.9 KiB ../node_modules/.pnpm/scheduler@0.23.2/node_modules/scheduler/cjs/scheduler.production.min.js
1.4 KiB ../node_modules/.pnpm/base64-js@1.5.1/node_modules/base64-js/index.js
1.3 KiB src/RootErrorBoundary.tsx
912 B ../node_modules/.pnpm/ieee754@1.2.1/node_modules/ieee754/index.js
789 B src/scenes/ChunkLoadErrorBoundary.tsx
762 B src/index.tsx
Largest files eagerly shipped from src/scenes/AuthenticatedShell.tsx
Size File
306.5 KiB ../node_modules/.pnpm/posthog-js@1.418.17/node_modules/posthog-js/dist/rrweb.js
267.7 KiB ../node_modules/.pnpm/@posthog+icons@0.38.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js
258.5 KiB ../node_modules/.pnpm/posthog-js@1.418.17/node_modules/posthog-js/dist/module.js
246.0 KiB src/taxonomy/core-filter-definitions-by-group.json
154.2 KiB ../node_modules/.pnpm/re2js@0.4.1/node_modules/re2js/build/index.esm.js
126.8 KiB ../node_modules/.pnpm/react-dom@18.3.1_react@18.3.1/node_modules/react-dom/cjs/react-dom.production.min.js
104.6 KiB src/lib/api.ts
95.1 KiB ../packages/quill/packages/quill/dist/index.js
93.3 KiB ../node_modules/.pnpm/prosemirror-view@1.40.1/node_modules/prosemirror-view/dist/index.js
90.6 KiB ../node_modules/.pnpm/@tiptap+core@3.20.6_@tiptap+pm@3.20.6/node_modules/@tiptap/core/dist/index.js

Posted automatically by check-eager-graph · sizes are eager output bytes (shipped, post-tree-shake) from the esbuild metafile · part of #32479

Toolbar bundle — eager 2.25 MiB within budget

What the toolbar ships to customer pages, measured from the esbuild output (minified, post-tree-shake). The eager set is the entry plus everything statically imported from it — fetched before any feature runs; deferred chunks load lazily. The eager guardrail is 5.72 MiB. Each output file must also stay below 10 MB, where CloudFront stops compressing it. The module boundary is enforced separately by check-toolbar-graph.

Metric Size Δ vs base Budget
Eager (shipped)
entry + static imports
2.25 MiB · 17 files 🔺 +47 B (+0.0%) ████░░░░░░ 39.3% of 5.72 MiB
Deferred (lazy) 2.09 MiB · 33 files no change n/a — loads on demand
Loader dist/toolbar.js 1.1 KiB no change █░░░░░░░░░ 5.8% of 19.5 KiB
Largest eagerly-shipped chunks
Size File
746.2 KiB dist/toolbar/toolbar-app-JDJU4DRU.css
582.9 KiB dist/toolbar/chunk-chunk-UJSUUJK2.js
484.6 KiB dist/toolbar/chunk-chunk-6S5AAQW2.js
133.8 KiB dist/toolbar/chunk-chunk-5NLGH2EL.js
131.8 KiB dist/toolbar/chunk-chunk-T5KY5WYR.js
71.2 KiB dist/toolbar/toolbar-app-QEF6IW4I.js
69.0 KiB dist/toolbar/chunk-chunk-27JL52RE.js
35.6 KiB dist/toolbar/chunk-chunk-OL2TGR3X.js
20.9 KiB dist/toolbar/chunk-chunk-YOYFPNOF.js
12.2 KiB dist/toolbar/chunk-chunk-PIK3PADE.js

Posted automatically by check-toolbar-size · sizes are toolbar output bytes (shipped, post-tree-shake) from the esbuild metafile

Dist folder size — 🔺 +2.2 KiB (+0.0%)

Total size of the built frontend/dist folder (all assets), compared against the base branch.

Total: 1441.95 MiB · 🔺 +2.2 KiB (+0.0%)

Playwright — all passed

All tests passed.

View test results →

@posthog
posthog Bot marked this pull request as ready for review August 26, 2026 17:31
@posthog

posthog Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

👋 Visual changes detected for this PR.

Review and approve in PostHog Visual Review

If these changes are unexpected, they may be caused by a flaky test or a broken snapshot on master. Don't approve — rerun the job or wait for a fix.

@trunk-io

trunk-io Bot commented Aug 26, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants