Required IAM Policies to Manage Collections
Review the IAM policies required to manage an Exadata Fleet Update collection of Oracle Exadata Database Service on Dedicated Infrastructure (ExaDB-D) or Oracle Exadata Database Service on Cloud@Customer (ExaDB-C@C) resources.
To use Oracle Cloud Infrastructure, you must be granted security access by an administrator using IAM policies. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don't have permission or are unauthorized, verify with your administrator what type of access you have and which compartment you should work in. If you're new to policies, see Getting Started with Policies and Common Policies.
Policies to Manage an Exadata Fleet Update Collection of Oracle Databases or CloudVmClusters on Oracle Exadata Database Service on Dedicated Infrastructure (ExaDB-D)
The following policies give permission to the example group CollectionAdmins to manage an Exadata Fleet Update collection of Oracle Databases or CloudVmClusters on Oracle Exadata Database Service on Dedicated Infrastructure (ExaDB-D). The statements provide the minimum access needed to complete administrative tasks with Exadata Fleet Update collections. Access is limited to resources in the specified example compartments.
allow group CollectionAdmins to manage fleet-software-update-discoveries in compartment ABC
allow group CollectionAdmins to manage fleet-software-update-collections in compartment ABC
allow group CollectionAdmins to read fleet-software-update-work-requests in compartment ABC
allow group CollectionAdmins to inspect database-software-images in compartment ABC
allow group CollectionAdmins to inspect db-homes in compartment ABC
allow group CollectionAdmins to inspect databases in compartment ABC
allow group CollectionAdmins to inspect cloud-exadata-infrastructures in compartment ABC
allow group CollectionAdmins to inspect db-nodes in compartment ABC
allow group CollectionAdmins to use cloud-vmclusters in compartment ABC
allow group CollectionAdmins to use vcns in compartment ABC
allow group CollectionAdmins to use subnets in compartment ABC
allow group CollectionAdmins to use vnics in compartment ABC
allow group CollectionAdmins to use private-ips in compartment ABC
allow group CollectionAdmins to use network-security-groups in compartment ABCIf you do not include
<identity_domain_name> before <group_name>, then the policy statement is evaluated as though the group belongs to the default identity domain.
Policies to Manage an Exadata Fleet Update Collection of Oracle Databases or VmClusters on Oracle Exadata Database Service on Cloud@Customer (ExaDB-C@C)
The following policies give permission to the example group CollectionAdmins to manage an Exadata Fleet Update collection of Oracle Databases or VmClusters on Oracle Exadata Database Service on Cloud@Customer (ExaDB-C@C). The statements provide the minimum access needed to complete administrative tasks with Exadata Fleet Update collections. Access is limited to resources in the specified example compartments.
allow group CollectionAdmins to manage fleet-software-update-discoveries in compartment ABC
allow group CollectionAdmins to manage fleet-software-update-collections in compartment ABC
allow group CollectionAdmins to read fleet-software-update-work-requests in compartment ABC
allow group CollectionAdmins to inspect database-software-images in compartment ABC
allow group CollectionAdmins to inspect db-homes in compartment ABC
allow group CollectionAdmins to inspect databases in compartment ABC
allow group CollectionAdmins to inspect exadata-infrastructures in compartment ABC
allow group CollectionAdmins to inspect vmclusters in compartment ABC
allow group CollectionAdmins to inspect db-nodes in compartment ABCIf you do not include
<identity_domain_name> before <group_name>, then the policy statement is evaluated as though the group belongs to the default identity domain.
Parent topic: Getting Started