Skip to content

Commit

Permalink
Updated installing aws file
Browse files Browse the repository at this point in the history
  • Loading branch information
CarmiWisemon committed Mar 14, 2024
1 parent 85f8751 commit 6bc0fff
Showing 1 changed file with 4 additions and 21 deletions.
25 changes: 4 additions & 21 deletions modules/installing-oadp-aws-sts.adoc
Original file line number Diff line number Diff line change
@@ -1,31 +1,16 @@
// Module included in the following assemblies:
//
// * backup_and_restore/application_backup_and_restore/oadp-rosa/oadp-rosa-backing-up-applications.adoc
// * backup_and_restore/application_backup_and_restore/oadp-aws/oadp-aws-backing-up-applications.adoc

:_mod-docs-content-type: PROCEDURE
[id="installing-oadp-aws-sts_{context}"]
= Installing the OADP Operator and providing the IAM role

AWS Security Token Service (AWS STS) is a global web service that provides short-term credentials for IAM or federated users. This document describes how to install {oadp-first} on an {aws-short} {sts-short} cluster manually.


[IMPORTANT]
====
Restic and Kopia are not supported in the OADP on ROSA with {aws-short} {sts-short} environment. Verify that the Restic and Kopia node agent is disabled.
For backing up volumes, OADP on ROSA with {aws-short} {sts-short} supports only native snapshots and Container Storage Interface (CSI) snapshots.
====

[IMPORTANT]
====
In an Amazon ROSA cluster that uses STS authentication, restoring backed-up data in a different {aws-short} region is not supported.
The Data Mover feature is not currently supported in ROSA clusters. You can use native {aws-short} S3 tools for moving data.
====

.Prerequisites

* An {product-title} ROSA cluster with the required access and tokens. For instructions, see the previous procedure _Preparing AWS credentials for OADP_. If you plan to use two different clusters for backing up and restoring, you must prepare {aws-short} credentials, including `ROLE_ARN`, for each cluster.
* An {product-title} {aws-short} {sts-short} cluster with the required access and tokens. For instructions, see the previous procedure _Preparing AWS credentials for OADP_. If you plan to use two different clusters for backing up and restoring, you must prepare {aws-short} credentials, including `ROLE_ARN`, for each cluster.
.Procedure

Expand Down Expand Up @@ -180,7 +165,7 @@ $ cat << EOF | oc create -f -
enable: false
EOF
----
<1> ROSA supports internal image backup. Set this field to `false` if you do not want to use image backup.
<1> Set this field to `false` if you do not want to use image backup.

// . Create the `DataProtectionApplication` resource, which is used to configure the connection to the storage where the backups and volume snapshots are stored:

Expand Down Expand Up @@ -228,7 +213,7 @@ $ cat << EOF | oc create -f -
provider: aws
EOF
----
<1> ROSA supports internal image backup. Set this field to false if you do not want to use image backup.
<1> Set this field to false if you do not want to use image backup.
<2> See the following note.
<3> The `credentialsFile` field is the mounted location of the bucket credential on the pod.
<4> The `enableSharedConfig` field allows the `snapshotLocations` to share or reuse the credential defined for the bucket.
Expand All @@ -239,8 +224,6 @@ You are now ready to back up and restore {product-title} applications, as descri

[NOTE]
====
The `enable` parameter of `restic` is set to `false` in this configuration, because OADP does not support Restic in ROSA environments.
If you use OADP 1.2, replace this configuration:
[source,terminal]
Expand Down

0 comments on commit 6bc0fff

Please sign in to comment.