From ca8757b2dd0459302e579fa9a5ff8976e2f87a5d Mon Sep 17 00:00:00 2001 From: Carmi Wisemon Date: Tue, 13 Feb 2024 12:55:09 +0200 Subject: [PATCH] OADP 3144 - Installing OADP on an AWS STS manually --- .../installing/installing-oadp-aws.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc b/backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc index ebd66485d057..f59821a0ce11 100644 --- a/backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc +++ b/backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc @@ -17,6 +17,9 @@ You configure AWS for Velero, create a default `Secret`, and then install the Da To install the OADP Operator in a restricted network environment, you must first disable the default OperatorHub sources and mirror the Operator catalog. See xref:../../../operators/admin/olm-restricted-networks.adoc#olm-restricted-networks[Using Operator Lifecycle Manager on restricted networks] for details. +You can also install OADP on an AWS Security Token Service (AWS STS) cluster manually. Amazon AWS provides AWS Security Token Service (AWS STS) as a web service that enables you to request temporary, limited-privilege credentials for users. You use STS to provide trusted users with temporary access to resources via API calls, your AWS console or the AWS command line interface (CLI). + + //include::modules/oadp-installing-operator.adoc[leveloffset=+1] include::modules/migration-configuring-aws-s3.adoc[leveloffset=+1] include::modules/oadp-about-backup-snapshot-locations-secrets.adoc[leveloffset=+1]