create-pipeline¶

Description¶

Creates a pipeline. A pipeline consumes messages from a channel and allows you to process the messages before storing them in a data store. You must specify both a channel and a datastore activity and, optionally, as many as 23 additional activities in the pipelineActivities array.

Synopsis¶

  create-pipeline
--pipeline-name <value>
--pipeline-activities <value>
[--tags <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]

Options¶

--pipeline-name (string)

The name of the pipeline.

--pipeline-activities (list)

A list of PipelineActivity objects. Activities perform transformations on your messages, such as removing, renaming or adding message attributes; filtering messages based on attribute values; invoking your Lambda unctions on messages for advanced processing; or performing mathematical transformations to normalize device data.

The list can be 2-25 PipelineActivity objects and must contain both a channel and a datastore activity. Each entry in the list must contain only one activity. For example:

pipelineActivities = [ { "channel": { ... } }, { "lambda": { ... } }, ... ]

(structure)

An activity that performs a transformation on a message.

channel -> (structure)

Determines the source of the messages to be processed.

name -> (string)

The name of the channel activity.

channelName -> (string)

The name of the channel from which the messages are processed.

next -> (string)

The next activity in the pipeline.

lambda -> (structure)

Runs a Lambda function to modify the message.

name -> (string)

The name of the lambda activity.

lambdaName -> (string)

The name of the Lambda function that is run on the message.

batchSize -> (integer)

The number of messages passed to the Lambda function for processing.

The Lambda function must be able to process all of these messages within five minutes, which is the maximum timeout duration for Lambda functions.

next -> (string)

The next activity in the pipeline.

datastore -> (structure)

Specifies where to store the processed message data.

name -> (string)

The name of the datastore activity.

datastoreName -> (string)

The name of the data store where processed messages are stored.

addAttributes -> (structure)

Adds other attributes based on existing attributes in the message.

name -> (string)

The name of the addAttributes activity.

attributes -> (map)

A list of 1-50 AttributeNameMapping objects that map an existing attribute to a new attribute.

Note

The existing attributes remain in the message, so if you want to remove the originals, use RemoveAttributeActivity .

key -> (string)

value -> (string)

next -> (string)

The next activity in the pipeline.

removeAttributes -> (structure)

Removes attributes from a message.

name -> (string)

The name of the removeAttributes activity.

attributes -> (list)

A list of 1-50 attributes to remove from the message.

(string)

next -> (string)

The next activity in the pipeline.

selectAttributes -> (structure)

Used to create a new message using only the specified attributes from the original message.

name -> (string)

The name of the selectAttributes activity.

attributes -> (list)

A list of the attributes to select from the message.

(string)

next -> (string)

The next activity in the pipeline.

filter -> (structure)

Filters a message based on its attributes.

name -> (string)

The name of the filter activity.

filter -> (string)

An expression that looks like a SQL WHERE clause that must return a Boolean value. Messages that satisfy the condition are passed to the next activity.

next -> (string)

The next activity in the pipeline.

math -> (structure)

Computes an arithmetic expression using the message’s attributes and adds it to the message.

name -> (string)

The name of the math activity.

attribute -> (string)

The name of the attribute that contains the result of the math operation.

math -> (string)

An expression that uses one or more existing attributes and must return an integer value.

next -> (string)

The next activity in the pipeline.

deviceRegistryEnrich -> (structure)

Adds data from the IoT device registry to your message.

name -> (string)

The name of the deviceRegistryEnrich activity.

attribute -> (string)

The name of the attribute that is added to the message.

thingName -> (string)

The name of the IoT device whose registry information is added to the message.

roleArn -> (string)

The ARN of the role that allows access to the device’s registry information.

next -> (string)

The next activity in the pipeline.

deviceShadowEnrich -> (structure)

Adds information from the IoT Device Shadow service to a message.

name -> (string)

The name of the deviceShadowEnrich activity.

attribute -> (string)

The name of the attribute that is added to the message.

thingName -> (string)

The name of the IoT device whose shadow information is added to the message.

roleArn -> (string)

The ARN of the role that allows access to the device’s shadow.

next -> (string)

The next activity in the pipeline.

Shorthand Syntax:

channel={name=string,channelName=string,next=string},lambda={name=string,lambdaName=string,batchSize=integer,next=string},datastore={name=string,datastoreName=string},addAttributes={name=string,attributes={KeyName1=string,KeyName2=string},next=string},removeAttributes={name=string,attributes=[string,string],next=string},selectAttributes={name=string,attributes=[string,string],next=string},filter={name=string,filter=string,next=string},math={name=string,attribute=string,math=string,next=string},deviceRegistryEnrich={name=string,attribute=string,thingName=string,roleArn=string,next=string},deviceShadowEnrich={name=string,attribute=string,thingName=string,roleArn=string,next=string} ...

JSON Syntax:

[
  {
    "channel": {
      "name": "string",
      "channelName": "string",
      "next": "string"
    },
    "lambda": {
      "name": "string",
      "lambdaName": "string",
      "batchSize": integer,
      "next": "string"
    },
    "datastore": {
      "name": "string",
      "datastoreName": "string"
    },
    "addAttributes": {
      "name": "string",
      "attributes": {"string": "string"
        ...},
      "next": "string"
    },
    "removeAttributes": {
      "name": "string",
      "attributes": ["string", ...],
      "next": "string"
    },
    "selectAttributes": {
      "name": "string",
      "attributes": ["string", ...],
      "next": "string"
    },
    "filter": {
      "name": "string",
      "filter": "string",
      "next": "string"
    },
    "math": {
      "name": "string",
      "attribute": "string",
      "math": "string",
      "next": "string"
    },
    "deviceRegistryEnrich": {
      "name": "string",
      "attribute": "string",
      "thingName": "string",
      "roleArn": "string",
      "next": "string"
    },
    "deviceShadowEnrich": {
      "name": "string",
      "attribute": "string",
      "thingName": "string",
      "roleArn": "string",
      "next": "string"
    }
  }
  ...
]

--tags (list)

Metadata which can be used to manage the pipeline.

(structure)

A set of key-value pairs that are used to manage the resource.

key -> (string)

The tag’s key.

value -> (string)

The tag’s value.

Shorthand Syntax:

key=string,value=string ...

JSON Syntax:

[
  {
    "key": "string",
    "value": "string"
  }
  ...
]

--cli-input-json | --cli-input-yaml (string) Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml.

--generate-cli-skeleton (string) Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. Similarly, if provided yaml-input it will print a sample input YAML that can be used with --cli-input-yaml. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command.

See ‘aws help’ for descriptions of global parameters.

Examples¶

Create an IoT Analytics Pipeline

The following create-pipeline example creates a pipeline. A pipeline consumes messages from a channel and allows you to process the messages before storing them in a data store. You must specify both a channel and a data store activity and, optionally, as many as 23 additional activities in the pipelineActivities array.

aws iotanalytics create-pipeline \
    --cli-input-json file://create-pipeline.json

Contents of create-pipeline.json:

{
    "pipelineName": "mypipeline",
    "pipelineActivities": [
        {
            "channel": {
                "name": "myChannelActivity",
                "channelName": "mychannel",
                "next": "myMathActivity"
            }
        },
        {
            "datastore": {
                "name": "myDatastoreActivity",
                "datastoreName": "mydatastore"
            }
        },
        {
            "math": {
                "name": "myMathActivity",
                "math": "((temp - 32) * 5.0) / 9.0",
                "attribute": "tempC",
                "next": "myDatastoreActivity"
            }
        }
    ],
    "tags": [
        {
            "key": "Environment",
            "value": "Beta"
        }
    ]
}

Output:

{
    "pipelineArn": "arn:aws:iotanalytics:us-west-2:123456789012:pipeline/mypipeline",
    "pipelineName": "mypipeline"
}

For more information, see CreatePipeline in the AWS IoT Analytics API Reference.

Output¶

pipelineName -> (string)

The name of the pipeline.

pipelineArn -> (string)

The ARN of the pipeline.

Table of Contents

Feedback

User Guide