-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RC: RDI In the Cloud #1066
base: main
Are you sure you want to change the base?
RC: RDI In the Cloud #1066
Conversation
Co-authored-by: andy-stark-redis <[email protected]>
Co-authored-by: andy-stark-redis <[email protected]>
Co-authored-by: andy-stark-redis <[email protected]>
Merging original work to clear pull request.
Co-authored-by: David Dougherty <[email protected]>
RDI in the Cloud: Add steps to set up AWS PrivateLink
this is great! Now sure if during private preview we should publish it online but more for internal use (staging or similar) |
@yaronp68 It's on staging, so that's what I've been giving people. I won't be merging this PR until we get to a public preview or something similar. |
Just for visibility - this is the Cloud Public Preview initiative - https://redislabs.atlassian.net/issues/RED-147332?filter=13199 Once it's released, we can merge this PR. |
@cmilesb Can we also create a FAQ page for the RDI Cloud somewhere? Maybe as as subsection? The first question that we can add is:
|
1. [Create an encryption key](#create-encryption-key) using AWS Key Management Service with the right permissions. | ||
1. [Create a secret](#create-database-credentials-secret) containing the source database credentials encrypted using that key. | ||
|
||
### Create encryption key |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cmilesb Lets put a big note here. 2 people from Redis already hit this issue when they are using Amazon RDS for the source database. And the issue they had was that they were using the AWS KMS managed key provided while creating the RDS instance.
But, You can't access an AWS KMS managed key-encrypted secret from another account.
The error that our team has seen was:
You can't access a secret from a different AWS account if you encrypt the secret with the default KMS service key.
The issue is described here - https://repost.aws/knowledge-center/secrets-manager-cross-account-key
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @yaronp68
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ZdravkoDonev-redis Just to clarify - this is a source database requirement? So should this be located under Prerequisites?
Replaces #570.
All new major changes to these docs should be approved and merged into the preview-rc-rdi branch via their own pull requests.
@yaronp68 FYI
Main staging links:
https://redis.io/docs/staging/preview-rc-rdi/operate/rc/databases/rdi/
https://redis.io/docs/staging/preview-rc-rdi/operate/rc/databases/rdi/define
https://redis.io/docs/staging/preview-rc-rdi/operate/rc/databases/rdi/setup
https://redis.io/docs/staging/preview-rc-rdi/operate/rc/databases/rdi/view-edit