Skip to content
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

aura api cloning #475

Merged
merged 11 commits into from
Oct 22, 2024
Merged

aura api cloning #475

merged 11 commits into from
Oct 22, 2024

Conversation

fiquick
Copy link
Contributor

@fiquick fiquick commented Sep 19, 2024

No description provided.

@fiquick
Copy link
Contributor Author

fiquick commented Sep 19, 2024

@fiquick fiquick added the WIP label Oct 1, 2024
Copy link
Collaborator

@AlexicaWright AlexicaWright left a comment

Choose a reason for hiding this comment

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

Some clarifications needed, but good and useful content!

@@ -55,10 +55,22 @@ For more information see the xref:auradb/importing/import-database.adoc#_neo4j_a
=== Clone an instance protected by CMK

To clone an instance protected by a Customer Managed Key, the key must be valid and available to Aura.
The cloned instance, by default, uses the available Customer Managed Key for that region and product.
If the same CMK does not exist in the destination region and product, the cloned instance must be encrypted with an available CMK for that region and product, which you can choose.
Copy link
Collaborator

Choose a reason for hiding this comment

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

What is it that you can choose? the key, the region, the product?

modules/ROOT/pages/platform/security/encryption.adoc Outdated Show resolved Hide resolved

.Summary of cloning restrictions
|===
| Cloning method | Destination key | Result
Copy link
Collaborator

Choose a reason for hiding this comment

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

The column Destination key is misleading. I see what you are trying to say, but either change the title of the column or how you phrase the contents.

@neo-technology-commit-status-publisher
Copy link
Collaborator

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

@fiquick fiquick merged commit dbe707c into main Oct 22, 2024
4 checks passed
@fiquick fiquick deleted the CMEKcloning branch October 22, 2024 14:49
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.

3 participants