API-Level Permissions for Dedicated AI Clusters
This page provides access and authorization information for the OCI Generative AI dedicated AI cluster resource type.
For specific permissions for this resource type, review this page. For a list of all resource types available in OCI Generative AI, see User Access to Individual Resources.
Resource Type
| Resource Type for IAM Permissions | Documentation Reference | API Reference |
|---|---|---|
generative-ai-dedicated-ai-cluster |
Managing Dedicated AI Clusters | DedicatedAiCluster |
Inspect Permission
Grant user groups inspect permission to run the following operations:
- GET
ListDedicatedAiClusters
Read Permission
Grant user groups read permission to run the following operations:
- GET
ListDedicatedAiClusters - GET
GetDedicatedAiCluster
Use Permission
Grant user groups use permission to run the following operations:
- GET
ListDedicatedAiClusters - GET
GetDedicatedAiCluster - PUT
UpdateDedicatedAiCluster
Manage Permission
Grant user groups manage permission to run the following operations:
- GET
ListDedicatedAiClusters - GET
GetDedicatedAiCluster - PUT
UpdateDedicatedAiCluster - POST
ChangeDedicatedAiClusterCompartment - POST
CreateDedicatedAiCluster - DELETE
DeleteDedicatedAiCluster
- The manage permission includes all actions allowed by use, read, and inspect.
- The use permission includes all actions allowed by read and inspect.
- The read permission includes all actions allowed by inspect.
The
generative-ai-dedicated-ai-cluster resource type is part of generative-ai-family. If you have permission to the family, you have the same permission for this resource type. For example:
allow group <your-group-name> to manage generative-ai-family
in compartment <your-compartment-name>1-1 Permissions for APIs
We recommend using the higher-level IAM verbs, manage, use, read, and inspect, for a better user experience. For example, you might grant a user group permission to delete a resource, but if you don't also grant permission to list that resource, users might not find it.
If a use case requires access to only a specific API operation, you can use the individual permissions listed here.
generative-ai-dedicated-ai-cluster
| Permission | API Operation | Operation Type | Verb |
|---|---|---|---|
GENERATIVE_AI_DEDICATED_AI_CLUSTER_INSPECT |
ListDedicatedAiClusters |
GET |
inspect |
GENERATIVE_AI_DEDICATED_AI_CLUSTER_READ |
GetDedicatedAiCluster |
GET |
read |
GENERATIVE_AI_DEDICATED_AI_CLUSTER_UPDATE |
UpdateDedicatedAiCluster |
PUT |
use |
GENERATIVE_AI_DEDICATED_AI_CLUSTER_MOVE |
ChangeDedicatedAiClusterCompartment |
POST |
manage |
GENERATIVE_AI_DEDICATED_AI_CLUSTER_CREATE |
CreateDedicatedAiCluster |
POST |
manage |
GENERATIVE_AI_DEDICATED_AI_CLUSTER_DELETE |
DeleteDedicatedAiCluster |
DELETE |
manage |
For example, the following two policies are equivalent:
allow group <your-user-group> to manage generative-ai-dedicated-ai-cluster
in compartment <your-compartment-name>allow group <your-user-group> to
{GENERATIVE_AI_DEDICATED_AI_CLUSTER_INSPECT, GENERATIVE_AI_DEDICATED_AI_CLUSTER_READ, GENERATIVE_AI_DEDICATED_AI_CLUSTER_UPDATE, GENERATIVE_AI_DEDICATED_AI_CLUSTER_MOVE, GENERATIVE_AI_DEDICATED_AI_CLUSTER_CREATE, GENERATIVE_AI_DEDICATED_AI_CLUSTER_DELETE}
in compartment <your-compartment-name>