Skip to content

OADP-5817: Removed incorrect information regarding SSE-C Encryption #90702

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 20, 2025
Merged

OADP-5817: Removed incorrect information regarding SSE-C Encryption #90702

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 1 addition & 15 deletions modules/oadp-ssec-encrypted-backups.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,26 +57,12 @@ The following procedure contains an example of a `spec:backupLocations` block th
$ dd if=/dev/urandom bs=1 count=32 > sse.key
----

.. Encode the `sse.key` by using Base64 and save the result as a file named `sse_encoded.key` by running the following command:
+
[source,terminal]
----
$ cat sse.key | base64 > sse_encoded.key
----

.. Link the file named `sse_encoded.key` to a new file named `customer-key` by running the following command:
+
[source,terminal]
----
$ ln -s sse_encoded.key customer-key
----

. Create an {product-title} secret:
** If you are initially installing and configuring {oadp-short}, create the AWS credential and encryption key secret at the same time by running the following command:
+
[source,terminal]
----
$ oc create secret generic cloud-credentials --namespace openshift-adp --from-file cloud=<path>/openshift_aws_credentials,customer-key=<path>/sse_encoded.key
$ oc create secret generic cloud-credentials --namespace openshift-adp --from-file cloud=<path>/openshift_aws_credentials,customer-key=<path>/sse.key
----
** If you are updating an existing installation, edit the values of the `cloud-credential` `secret` block of the `DataProtectionApplication` CR manifest, as in the following example:
+
Expand Down