Repository navigation
RC: Self-managed encryption keys Private Preview branch - #1740
Merged
Merged
Conversation
RC: Self-managed encryption private preview - Google Cloud and Subscription creation
Contributor
RC: Self-managed encryption keys - AWS
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
|
Cameron Bates seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
mich-elle-luna
marked this pull request as ready for review
September 14, 2026 18:00
mich-elle-luna
requested review from
a team
and removed request for
joniredis
September 14, 2026 18:01
dwdougherty
approved these changes
Sep 14, 2026
dwdougherty
left a comment
Collaborator
There was a problem hiding this comment.
Language LGTM. Several of the GC links came up in French language; not sure why. Probably good to confirm on your end.
- Point Google Cloud documentation links at docs.cloud.google.com. - Say Redis uses the key for storage encryption and for recovery. - Add a section on rotating key material or key versions, and note that changing to a different key isn't supported. - List every deletion grace period option, including the timed ones, in the final steps and in Revoke key access. - Add Active-Active guidance for keys per region, with a screenshot of the per-region key resource name fields. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
🧠 Redis MemoryFound 8 related items from repository history (1 new this commit):
Memory updated at 9ca3f41 |
Also say that all persistent data on Redis Cloud is encrypted at rest, rather than all data. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
An earlier merge resolution kept both sides of create-pro-database-new.md. The Advanced options table had a blank line after the header row, which ended the table there, plus duplicate VPC configuration and Public endpoint access rows and a stale Cloud account row. The page had also reverted main's Markdown images to the older image shortcode. Take main's version and re-add the Persistent storage encryption row after Public endpoint access, so the page differs from main by that one row. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
EliShteinman
pushed a commit
to EliShteinman/docs
that referenced
this pull request
Oct 15, 2026
The CMEK pages were written while the {{< image >}} shortcode still
existed. main has since converted every image to Markdown syntax and
removed the shortcode, so merging preview-cmek (redis#1740) broke the build:
content/embeds/rc-cmek-final-steps.md:14:5: failed to extract
shortcode: template for shortcode "image" not found
Convert the six remaining uses, five in manage-encryption-keys.md and one
in the rc-cmek-final-steps embed, to  plus a
{width="..."} attribute line, keeping the alt text and widths. make ci
passes on main with this change.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
EliShteinman
added a commit
to EliShteinman/docs
that referenced
this pull request
Oct 15, 2026
Add the Redis Cloud self-managed encryption keys (CMEK) private preview page for AWS and Google Cloud. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
This is a draft PR for the preview of Customer-managed encryption keys. Will be merged to main for public preview.
Note
Low Risk
Documentation-only changes for a preview feature; no application code, auth, or data paths are modified.
Overview
Adds Redis Cloud Pro self-managed (customer-managed) persistent storage encryption documentation for the private preview, including a new security guide and wiring into the Pro database creation flow.
The new
manage-encryption-keys.mdpage covers prerequisites, enabling Customer managed key on a new Pro subscription (pending state until key access is granted, 7-day cleanup), AWS and Google Cloud key policy/IAM steps, shared final steps viarc-cmek-final-steps.md(deletion grace period options, SLA warning for alert-only, Activate), key rotation limits (no ARN swap), and behavior when key access is revoked.create-pro-database-new.mddocuments Persistent storage encryption under Setup advanced options and links to the new guide. It also replaces Hugo{{<image>}}shortcodes with standard Markdown images and separate{width=...}attribute lines across the page.Reviewed by Cursor Bugbot for commit 9ca3f41. Bugbot is set up for automated code reviews on this repo. Configure here.