[ZdravkoDonev-redis]

Correct the database PrivateLink setup instructions and show the recommended connection path.

Changes

• Use TCP on the database port, with PostgreSQL port 5432 beside the settings.
• Give the NLB its own security group. Split inbound and outbound instructions.
• Allow database connections and TCP health checks from the NLB security group.
• Replace "static IP" with the current writer address. Link to the existing failover Lambda.
• State that the target Redis Cloud Pro database must already exist.
• Move the RDS Proxy diagram to the RDS Proxy page. Keep its PostgreSQL limitation visible.
• Add an editable SVG for the direct NLB connection and Lambda updates.

Read The Diagram

• Solid arrows: RDI connects through PrivateLink and the NLB to the database writer.
• Dashed arrows: RDS events reach SNS, which invokes Lambda.
• Lambda resolves the writer endpoint and updates the target group.
• Lambda does not carry database traffic.

The diagram follows the existing Redis Lambda module. The text uses short instructions and separates database connections from address updates.

Validation

• git diff --check passed.
• SVG XML and image references passed. Rendered SVG visually checked.
• Focused Hugo rendering passed with the repository image hook, parser settings, and tabs (Hugo 0.154.2).
• Verified the proxy image appears only on the proxy page and the Lambda anchor still works.
• Full-site local build was stopped before completion. The PR site build remains a separate check.
• AWS setup walkthrough and RDI connectivity qualification remain pending. Keep this PR in draft until those steps pass.

Ticket: RDSC-6239. SQL grants: #4293.

---

Note

Low Risk
Documentation and diagram assets only; no application or infrastructure code changes.

Overview
Corrects Redis Cloud RDI PrivateLink setup docs so they match the recommended path: TCP to the database writer through a dedicated NLB security group, with optional Lambda keeping the IP target group current after RDS failover.

In setup.md, the guide now tells readers to create the target Redis Cloud Pro database first, swaps the RDS/Aurora architecture image for a new SVG that separates database traffic (solid) from SNS → Lambda target-group updates (dashed), and rewrites EC2 and RDS/Aurora NLB steps—Custom TCP and port 5432 for PostgreSQL, NLB-specific target group docs, TCP health checks, writer DNS instead of a “static IP,” and inbound rules sourced from the NLB security group rather than open HTTP. The RDS/Aurora tab frames Lambda as address maintenance, not a proxy for query traffic, and tightens the RDS Proxy callout.

On rds-proxy.md, the former shared Aurora diagram moves here with an explicit non-PostgreSQL note for the proxy alternative.

^{Reviewed by Cursor Bugbot for commit f9d3c3e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

🧠 Redis Memory

Found 8 related items from repository history:

• PR — RC: Document connecting to PrivateLink from on-premises

  The guide only covered consumers inside the consumer VPC and didn't explain that the console's public endpoint hostname resolves to the Redi

• PR — DOC-6845: Add MongoDB Atlas Private Link tab to Cloud RDI setup guide

  Documents the two-way handshake flow for connecting a MongoDB Atlas source database to Cloud RDI via Private Link: get the Atlas endpoint se

• Commit — Staging links:
  https://redis.io/docs/staging/joniredis-privatelink-ga/operate/rc/security/aws-privatelink/

  Staging links:
  https://redis.io/docs/staging/joniredis-privatelink-ga/operate/rc/security/aws-privatelink/

• PR — Explain Cloud RDI networking for multiple sources and subscriptions

  Cloud RDI networking docs currently show only one source connection. Expand the existing overview to explain shared and separate PrivateLink

• Commit — Staging links:
  https://redis.io/docs/staging/joniredis-privatelink-limitations-updates/operate/rc/security/aws-priva

  Staging links:
  https://redis.io/docs/staging/joniredis-privatelink-limitations-updates/operate/rc/security/aws-privatelink/

• Commit — RDSC-6239: Correct database PrivateLink setup instructions

  RDSC-6239: Correct database PrivateLink setup instructions

• PR — RDSC-6239: Clarify PostgreSQL future table grants

  Fix future-table read grants for PostgreSQL, including on-premises and Aurora. Update both current and 1.19.1 pages.

• Commit — RDSC-6239: Show direct PrivateLink connectivity and Lambda updates

  RDSC-6239: Show direct PrivateLink connectivity and Lambda updates

Memory updated at f9d3c3e

[github-actions]

Staging links:
https://redis.io/docs/staging/RDSC-6239-aurora-networking/operate/rc/rdi/setup/

[ZdravkoDonev-redis]

@andy-stark-redis Please review and if you're OK directly merge. Another PR which addresses feedback about our docs.

Also the CI stage that fails - I think it's not cause by my PR changes?

[mich-elle-luna]

thank you!