Details for the Streaming Service

This topic covers details for writing policies to control access to the Streaming service.

Resource-Types

streams

stream-pull

stream-push

Supported Variables

The Streaming service supports all the general variables (see General Variables for All Requests) plus the following:

The streams resource type can use the following variables:

Variable Variable Type Source
target.stream.id Entity (OCID) Request

Details for Verb + Resource-Type Combinations

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. A plus sign (+) in a table cell indicates incremental access compared to the cell directly above it, whereas "no extra" indicates no incremental access.
streams
Verbs Permissions APIs Fully Covered APIs Partially Covered
inspect

STREAM_INSPECT

ListStreams

none

read

STREAM_READ

GetStream

none

use

no extra

no extra

none

manage

USE +

STREAM_CREATE

STREAM_DELETE

STREAM_UPDATE

CreateStream

DeleteStream

UpdateStream

none

stream-pull
Verbs Permissions APIs Fully Covered APIs Partially Covered
inspect

none

none

none

read

none

none

none

use

STREAM_CONSUME

GetMessages

CreateCursor

CreateGroupCursor

GetGroup

UpdateGroup

ConsumerHeartbeat

ConsumerCommit

none

manage

no extra

no extra

none

stream-push
Verbs Permissions APIs Fully Covered APIs Partially Covered
inspect

none

none

none

read

none

none

none

use

STREAM_PRODUCE

PutMessages

none

manage

no extra

no extra

none

Permissions Required for Each API Operation

API Operation Permissions Required to Use the Operation
ListStreams STREAM_INSPECT
CreateStream STREAM_CREATE
GetStream STREAM_READ
DeleteStream STREAM_DELETE
GetMessages STREAM_CONSUME
PutMessages STREAM_PRODUCE
UpdateStream STREAM_UPDATE
CreateCursor STREAM_CONSUME
CreateGroupCursor STREAM_CONSUME
GetGroup STREAM_CONSUME
UpdateGroup STREAM_CONSUME
ConsumerHeartbeat STREAM_CONSUME
ConsumerCommit STREAM_CONSUME