Skip to content

RDSC-5962: Document AWS CIDR requirements for Cloud RDI workspaces - #3834

Open
ZdravkoDonev-redis wants to merge 1 commit into
mainfrom
RDSC-5962-aws-rdi-workspace-cidr
Open

RDSC-5962: Document AWS CIDR requirements for Cloud RDI workspaces#3834
ZdravkoDonev-redis wants to merge 1 commit into
mainfrom
RDSC-5962-aws-rdi-workspace-cidr

Conversation

@ZdravkoDonev-redis

@ZdravkoDonev-redis ZdravkoDonev-redis commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Document that each Cloud RDI workspace uses a dedicated /22 CIDR.
  • Explain the AWS requirement to use the same RFC 1918 private range as the subscription VPC primary CIDR.
  • Describe non-overlap requirements and include valid and invalid examples.
  • Link to the AWS VPC CIDR association restrictions.

Why

AWS rejects a secondary VPC CIDR when it is in a different RFC 1918 range from the VPC primary CIDR. The previous documentation only said that the CIDR must not conflict with applications or databases, so it did not provide enough guidance when the automatic suggestion was missing or unsuitable.

User impact

The shared workspace creation content is used by both the Cloud RDI workspace page and the quick start. Users now have the same CIDR selection guidance in both places.

Validation

  • git diff --check
  • Rendered both affected pages with Hugo v0.143.1 and verified the /22, same-range, non-overlap, example, and link content in the generated HTML.
  • Verified the RFC 1918 and AWS restriction links return HTTP 200.
  • The full repository build reaches and renders both affected pages, then stops on unrelated missing generated examples in existing client documentation.

Jira: https://redislabs.atlassian.net/browse/RDSC-5962


Note

Low Risk
Documentation-only change to RDI workspace creation guidance; no application or infrastructure code.

Overview
Expands the shared Create workspace embed (rc-rdi-create-rdi-workspace.md) so step 3 documents dedicated /22 CIDRs per RDI workspace and AWS-specific rules when auto-suggestion is missing or wrong.

AWS guidance added: the workspace CIDR must stay in the same RFC 1918 private range as the subscription VPC primary CIDR, must not overlap subscription/peering/TGW/app/database/other workspace ranges, includes valid/invalid examples (e.g. 10.238.252.0/24 VPC vs 192.168.0.0/22 vs 10.239.0.0/22), and links to AWS VPC CIDR association restrictions. A trailing newline fix is included on the closing paragraph.

Because the embed is reused on create-workspace and quick-start, both flows get the same CIDR guidance.

Reviewed by Cursor Bugbot for commit 0f979f4. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

@ZdravkoDonev-redis ZdravkoDonev-redis self-assigned this Aug 19, 2026
@ZdravkoDonev-redis
ZdravkoDonev-redis marked this pull request as ready for review August 19, 2026 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant