Policies for Other Services Managed by Full Stack Disaster Recovery
Full Stack DR service implements DR workflows by managing other OCI resources that are part of the application stack. Set up the policies according to your use case. For example, for Oracle Database, ensure to configure policies for Vault. Similarly, for Compute service, ensure to configure policies for Oracle Cloud Agent.
To enable DR service to manage these OCI resources, you must configure policy-based access to allow access to these resources. Refer to How Policies Work to learn about general concepts of the IAM policies before defining the IAM policies for DR.
- Policies for Compute Service and Oracle Cloud Agent To allow Disaster Recovery (DR) to manage compute instances during DR, you must set up policies for Compute Instances and for Oracle Cloud Agent.
- Policies for Block Volume Service Shows how to allow Disaster Recovery (DR) to manage block storage volumes and volume groups that are part of the application stack.
- Policies for Networking Service Shows how to allow Disaster Recovery (DR) to manage networking components for compute instances that are part of the application stack.
- Policies for Functions Service Shows how to allow Disaster Recovery (DR) to invoke Oracle Functions as part of a user-defined step in a DR plan.
- Policies for Oracle Database Shows how to allow Disaster Recovery (DR) to manage DR for Oracle Base Database, Oracle Exadata Database Service on Dedicated Infrastructure, Oracle Exadata Database Service on Exascale Infrastructure, Oracle Exadata Database Service on Cloud@Customer databases that are part of the application stack.
- Policies for Oracle Autonomous Database Shows how to allow Disaster Recovery (DR) to manage Oracle Autonomous Database Service databases such as Oracle Autonomous Database Serverless and Autonomous Database on Dedicated Exadata Infrastructure (Autonomous Container Database) that are part of the application stack.
- Policies for Log Location for Operation Logs Shows how to allow Disaster Recovery (DR) to manage Object Storage buckets and objects. This access is required to write logs to Object Storage during DR plan executions.
- Policies for Object Storage Shows how to allow Disaster Recovery (DR) to manage Object Storage buckets and objects. This access is required to:
- Policies for Tags Service Shows how to allow Disaster Recovery (DR) to use Tag namespaces. This access is required when launching compute instances as part of DR plan executions.
- Policies for Vault Service Shows how to allow Disaster Recovery (DR) to use the Vault service. This access is required when reading Exadata and Enterprise database passwords required for DR plan executions.
- Policies for File Systems Shows how to allow Disaster Recovery (DR) to manage file systems that are part of the application stack.
- Policies for Load Balancers Shows how to allow Disaster Recovery (DR) to manage load balancers that are part of the application stack.
- Policies for Kubernetes Engine (OKE) Shows how to allow Disaster Recovery (DR) to manage Kubernetes Engine (OKE) that is part of the application stack.
- Policies for MySQL HeatWave DB System Shows how to allow Disaster Recovery (DR) to manage MySQL DB System that is part of the application stack.
- Policies for PostgreSQL DB System Shows how to allow Disaster Recovery (DR) to manage PostgreSQL DB System that is part of the application stack.
- Policies for Network Load Balancers Shows how to allow Disaster Recovery (DR) to manage network load balancers that are part of the application stack.
- Policies for Compartments Shows how to allow Disaster Recovery (DR) to manage compartments (or the tenancy) that contain resources that are part of the application stack.
- Policies for Automatic DR Configuration Resource Principal is the pre-requisite for configuring Automatic DR.
- Policies for Integration Instance Shows how to allow Disaster Recovery (DR) to manage integration instances that are part of the application stack.
- Policies for Generative AI Shows how to allow Disaster Recovery (DR) to manage Generative AI that are part of the application stack.