IDs of Entities - AWS Elemental Conductor Live 3

This is version 3.17 of the AWS Elemental Conductor Live 3 documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Conductor Live 3 Documentation.

IDs of Entities

When an entity is created, it is automatically assigned an ID that is stored in the <id></id> element.

These unique IDs are typically shown on the AWS Elemental Conductor Live 3 web interface under the “ID” column.

Obtaining an ID

The ID is shown in the POST response and can be obtained using GET List. To obtain an ID:

  • Obtain a list of IDs for an entity using a GET request.

  • Parse the response for the desired ID by looking for the ID that corresponds to a piece of data that you specified, such as the entity name.

The ID must be passed in any PUT, GET, and DELETE. In general, you cannot identify an entity using the name element.

Multiple Identities

Conductor systems and worker nodes within a cluster are assigned a node ID. Redundancy group membership assigns a redundancy member ID. It is important that you not conflate the node ID with the redundancy member ID; they are different IDs.

Any element that is a grouping of attributes is usually assigned a unique ID. The presence of this ID does not mean you can query this grouping by passing in this ID. You can only query the entities listed in Entities, Attributes, Elements, Properties, Parameters.

Uniqueness of IDs

Each type of entity has its own numbering scheme. For example, redundancy groups are numbered from 1 and channels are numbered separately, starting from 1.

Numbering increments indefinitely. If an entity is deleted, its number is not recycled.