The following tables show the permissions and API operations covered by each verb. The level of access is cumulative as you go from inspect > read > use > manage. For example, a group that can use a resource can also inspect and read that resource. A plus sign (+) in a table cell indicates incremental access compared to the cell directly above it, whereas "no extra" indicates no incremental access.
For example, the read verb for network-load-balancers includes the same
permissions and API operations as the inspect verb, plus the
NETWORK_LOAD_BALANCER_READ permission and various API operations (e.g.,
GetNetworkLoadBalancer, ListWorkRequests, and so
forth.). The use verb covers more permissions and sets of API
operations compared to read. And manage covers more
permissions and API operations compared to use.
network-load-balancers
Verbs
Permissions
APIs Fully Covered
APIs Partially Covered
inspect
NETWORK_LOAD_BALANCER_INSPECT
ListNetworkLoadBalancers
none
read
INSPECT +
NETWORK_LOAD_BALANCER_READ
INSPECT +
GetNetworkLoadBalancer
ListListeners
GetListener
ListBackendSets
GetBackendSet
ListBackends
GetBackend
GetHealthChecker
ListNetworkLoadBalancersHealth
GetNetworkLoadBalancersHealth
GetBackendSetHealth
GetBackendHealth
ListPolicies
ListProtocols
ListWorkRequests
GetWorkRequest
ListWorkRequestErrors
ListWorkRequestLogs
none
use
READ +
NETWORK_LOAD_BALANCER_UPDATE
READ +
UpdateNetworkLoadBalancer
UpdateNetworkSecurityGroups
UpdateListener
UpdateBackendSet
UpdateBackend
UpdateHealthChecker
none
manage
USE +
NETWORK_LOAD_BALANCER_CREATE
NETWORK_LOAD_BALANCER_DELETE
NETWORK_LOAD_BALANCER_MOVE
USE +
CreateNetworkLoadBalancer
DeleteNetworkLoadBalancer
ChangeNetworkLoadBalancerCompartment
CreateListener
DeleteListener
CreateBackendSet
DeleteBackendSet
CreateBackend
DeleteBackend
none
Permissions Required for Each API Operation 🔗
The following table lists the API operations in a logical order, grouped by resource type.
For information about permissions, see Permissions.