Push Cloud Services Channels

AWS Kinesis

Partners can use AWS Kinesis channel to push events to an AWS Kinesis Data Stream.

• Events can be encoded as JSON or as Protocol Buffers (protobuf).

• Events are terminated by a newline character when its encoded as JSON.

  Note	For sample JSON format events, refer to Sample Events JSON format. For detailed Protobuf spec, refer to the gRPC Service Spec/Protobuf Definition.

You must provide the following details to configure the Cisco DNA Spaces Firehose API to push data into an AWS Kinesis Data Stream.

• AWS Region

• Kinesis Firehose Data Stream Name

• AWS Access Key

• AWS Secret Key

AWS Kinesis Firehose

Partners can use the AWS Kinesis Firehose channel to push events to an AWS Kinesis Data Firehose.

• Events can be encoded as JSON or as Protocol Buffers (protobuf).

• Events are terminated by a newline character when its encoded as JSON

  Note	For sample JSON format events, refer to Sample Events JSON format. For detailed Protobuf spec, refer to the gRPC Service Spec/Protobuf Definition.

You must provide the following details to configure the Cisco DNA Spaces Firehose API to push data into an AWS Kinesis Data Firehose:

• AWS Region

• Kinesis Firehose Delivery Stream Name

• AWS Access Key

• AWS Secret Key

Azure Event Hubs

Partners can use Azure Event Hub channel to push events to an Azure Event Hub.

• Events can be encoded as JSON or as Protocol Buffers (protobuf).

• Events are terminated by a newline character when its encoded as JSON

  Note	For sample JSON format events, refer to Sample Events JSON format. For detailed Protobuf spec, refer to the gRPC Service Spec/Protobuf Definition.

You must provide the following details to configure the Cisco DNA Spaces Firehose API to push data into the Azure Event Hubs:

• Connection String

Google Pub-Sub

Partners can use Google Pub/Sub channel to push events to a Google Pub/Sub topic.

• Events can be encoded as JSON or as Protocol Buffers (protobuf).

• Events are terminated by a newline character when its encoded as JSON.

  Note	For sample JSON format events, refer to Sample Events JSON format. For detailed Protobuf spec, refer to the gRPC Service Spec/Protobuf Definition.

Partner needs to allow partner-api@dna-spaces.iam.gserviceaccount.com to publish events to the Pub/Sub topic.

Once access is provided, the following details about the Pub/Sub topic are needed to configure Cisco DNA Spaces Firehose API to push data into the Pub/Sub topic:

• Project ID

• Topic