A tenancy administrator can create policies in Oracle Cloud Infrastructure Identity and Access Management (IAM) to grant permissions to groups on resources in compartments in a tenancy.

For example, you can create an Administrators group whose members can access all Database Migration resources. You can then create a separate group for everyone else who's involved with Database Migration, and create policies that restrict their access to Database Migration resources in different compartments.

For a complete list of Oracle Cloud Infrastructure policies, see policy reference.

A policy is a document that consists of one or more statements. A policy statement follows this basic syntax:

Allow group <group_name> to <verb><resource-type> in compartment <compartment_name>

Policy language uses simple verbs like inspect, read, use, and manage.

Database Migration offers individual resource-types for writing policies.

When you add conditions to your policies, you can use either Oracle Cloud Infrastructure general or service specific variables.

Database Migration supports all general variables. For more information, see general variables for all requests.

There are various Oracle Cloud Infrastructure verbs and resource-types that you can use when you create a policy. The topics in this section show the permissions and API operations covered by each verb for Database Migration.

The level of access is cumulative as you go from inspect to read to use to manage.

Here's a list of the API operations for Oracle Cloud Infrastructure Database Migration in logical order, grouped by resource-type.

The resource-types are odms-agent, odms-connection, odms-job and odms-migration.

1. In the Console navigation menu, under Identity & Security, go to Identity, and then click Policies.
2. Click Create Policy.
3. Enter a name and description for the policy.
4. Select the compartment. If you want to attach the policy to a compartment other than the one you're viewing, select it from list.
5. Select Database Migration Service in the Policy use cases option in the policy builder.
6. Select the template that best matches your requirements from the Common policy templates list. The policy builder displays the description of the chosen policy and lists the policy statements that it includes. The following policies are available for the Database Migration Service:
   • Let users manage required database migration resources along with all other required resources/networking- This is recommended for Database Migration Service and other required OCI resources.
   • Let users manage database migration resources with networking
   • Let users manage database migration resources without networking
   • Let users use database migration service resources
   • Let users manage database migration resources with networking if the manage virtual-network-family policy is restricted.
7. Select the group and the location.
8. Select Show manual editor if you already know how to write the statements you need and you want to enter them in a text box.
9. To add tags to this policy, click Show advanced options.
10. If you want to create another policy, select Create another policy.
11. Click Create.

Allow group {group name} to manage odms-connection in  {location}
Allow group {group name} to manage odms-migration in {location}
Allow group {group name} to manage odms-job in {location}
Allow group {group name} to manage goldengate-connections in {location}
Allow group {group name} to manage virtual-network-family in {location}
Allow group  {group name} to manage tag-namespaces in {location}
Allow group {group name}  to manage vaults in {location}
Allow group {group name}  to manage keys in {location}
Allow group {group name} to manage secret-family in {location}
Allow group {group name} to manage object-family in {location}

Allow group {group name} to manage virtual-network-family in compartment {compartment name}
Allow group {group name} to manage vaults in compartment {compartment name}
Allow group {group name} to manage keys in compartment {compartment name}
Allow group {group name} to manage secret-family in compartment {compartment name}
Allow group {group name} to manage object-family in compartment {compartment name}
Allow group {group name} to manage odms-connection in compartment {compartment name} 
Allow group {group name} to manage odms-migration in compartment {compartment name} Allow group {group name} to manage odms-job in compartment {compartment name}

For scenarios where Manage virtual-network-family cannot be assigned, it can be substituted by:

Allow group {group name}  to inspect vcns in compartment {compartment name}
Allow group {group name}  to use subnets in compartment {compartment name}
Allow group {group name}  to manage vnic in compartment {compartment name}

Depending on whether or not you intend to use the following services, you will need to add policies to enable access to these services as well:

• Oracle Autonomous Databases for your target databases:

  Allow group {group name} to manage database-family in compartment {compartment name} → Aggregate resource type

• Base database for your source or target:

  Allow group {group name} to manage autonomous-database-family in compartment {compartment name} →Aggregate resource type

• If you need to access the connections created by GoldenGate integrated service:

  Allow group {group name} to manage GoldenGate-connections in compartment {compartment name}

• If you need to deploy your own GoldenGate Marketplace instance and use as an advanced replication option:

  Allow group {group name} to manage instance-family in compartment {compartment name}
  Allow group {group name} to manage volume-family in compartment {compartment name}
  Allow group {group name} to manage public-ips in compartment {compartment name}
  Allow group {group name} to use tag-namespaces in tenancy
  Allow group {group name} to inspect compartments in tenancy
  Allow group {group name} to manage orm-family in compartment {compartment name}
  Allow group {group name} to manage app-catalog-listing in compartment {compartment name}→ Required to launch the GG marketplace stack

Policies define what actions members of a group can perform, and in which compartments. You create policies using the Oracle Cloud Console. In the Oracle Cloud Console navigation menu, under Identity & Security and then under Identity, click Policies. Policies are written in the following syntax:

Allow group <group-name> to <verb> <resource-type> in <location> where <condition>

• <group-name>: The name of the user group you're giving permissions to
• <verb>: Gives the group a certain level of access to a resource-type. As the verbs go from inspect to read to use to manage, the level of access increases and the permissions granted are cumulative.
• <resource-type>: The type of resource you're giving a group permission to work with, such as odms-agent, odms-connection, odms-job, and odms-migration.

  For more information, see resource-types.

• <location>: Attaches the policy to a compartment or tenancy. You can specify a single compartment or compartment path by name or OCID, or specify tenancy to cover the entire tenancy.
• <condition>: Optional. One or more conditions for which this policy will apply.

allow group <group-name> to inspect virtual-network-family in compartment <compartment-name>

allow group <group-name> to manage tag-namespaces in compartment <compartment-name>