Contents
Cirrus Link Resources
Cirrus Link Website
Contact Us (Sales/Support)
Forum
Cirrus Link Modules Docs for Ignition 7.9.x
Inductive Resources
Ignition User Manual
Knowledge Base Articles
Inductive University
Forum
Page History
...
| Anchor | ||||
|---|---|---|---|---|
|
Once you have Ignition and the AWS Injector Module installed and running we can setup the configuration to connect to AWS.
| Tip |
|---|
| Review theAWS Injector Module configuration guide for more details on each tab |
Navigate to the AWS Injector Module configuration section from the left side bar in the Ignition Gateway.
...
| Note |
|---|
| For this tutorial, we will be adding new Kinesis Stream and DynamoDB Database Settings. You may optionally choose to skip one of the following two sections if you do not wish to setup a Kinesis Stream endpoint or |
...
| a DynamoDB Database. |
| Anchor | ||||
|---|---|---|---|---|
|
...
Click on "Create New DynamoDB Setting" to finish creating the new configuration setting.
Now the AWS Injector module is connected to a Kinesis Stream and/or a DynamoDB Database, we have to determine if there are are changes needed to the Tab Agent tab to be able to push data.
| Tip |
|---|
| If you already have Ignition tags defined, for example from the Ignition OPC UA Server, then depending on the depth of your tag tree you may need to configure the Sparkplug Settings. Review the Cloud Injector Tag Agents and Tag Trees document which describes how Cloud Injector Agent configurations interact with Ignition tag trees to push messages and tag change events to the cloud service. It explains how tags get identified to be pushed as well as what specific 'topics' will be included with the messages. It also goes over some example configurations to show how the system will behave in different scenarios. |
Once the Tag Agent is setup as needed, you can jump to Step 3: Publishing data.
If you do not have Ignition tags defined we will do that in the next step with a tag tree depth that requires no additional Sparkplug settings.
Step 2: Create tags to be published in Designer
When the AWS Injector module is installed in Ignition, an Edge Node folder is automatically created in the 'default' Ignition tag provider.
Create a tree structure under this folder as shown below with some memory tags - this folder structure creates the same hierarchy that is described in the Sparkplug B specification of Group ID, Edge ID, and Device ID.
| Tip |
|---|
| Refer to the Ignition Tag Browser and Creating Tags documentation for assistance in configuring Ignition tags |
Step 3: Publishing data
When the AWS Injector module is installed in Ignition, an AWS Injector tag provider is automatically created. This folder will contain both information tags about the module's version and state, as well as control tags for refreshing the module and Tag Agents.
Make sure that the Ignition Designer has read/write communications turned on by selecting the Project/Comm Read/Write button highlighted in the image below. 
| Tip |
|---|
| Review the Inductive Automation Designer documentation for additional assistance on setting the project communication mode |
To refresh the default Tag Agent, open the folder "AWS Injector Control" and click on the Refresh Boolean. When this happens, the Tag Agent will scan the "Edge Nodes" folder and find the new Memory Tags that we have created, construct messages representing those tags with their current values and send the messages to the Kinesis Stream and/or DynamoDB Database that we have configured.
| Note |
|---|
| The Boolean tag will not change to true. This is really a one-shot and as a result, the tag will not change to true. |
...
Overview
Content Tools