Anomaly Detection Policies

Resource Types 🔗

Anomaly Detection offers both aggregate and individual resource-types for writing policies. You can use aggregate resource types to write fewer policies. For example, instead of allowing a group to manage all individual resource types, you can have a policy that allows the group to manage the aggregate resource type, ai-service-anomaly-detection-family.

Individual Resource Types

Copy

ai-service-anomaly-detection-model
ai-service-anomaly-detection-project
ai-service-anomaly-detection-data-asset
ai-service-anomaly-detection-private-endpoint
ai-service-anomaly-detection-job

Aggregate Resource Type

Copy

ai-service-anomaly-detection-family

Required IAM Policy 🔗

To work with Anomaly Detection, an administrator must grant you access in an IAM policy.

If you get a message that you don’t have permission or are unauthorized, verify with an administrator what type of access you have.

Create a policy with one of the following policies:

allow <subject> to manage ai-service-anomaly-detection-family in tenancy, where subject can be:
group <group-name> | group id <group-ocid> | dynamic-group <dynamic-group-name> | dynamic-group id <dynamic-group-ocid> | any-user

Example Policies 🔗

Allow users to manage all Anomaly Detection resources using the aggregate resource:

allow any-user to manage ai-service-anomaly-detection-family in tenancy

Resource Types and Permissions 🔗

Permissions Required for Each API Operation 🔗

You can use the individual resource types with API calls to interact with the service.

The following table lists the API operations for the Anomaly Detection service in a logical order, grouped by resource type, and the permissions required for resource types: