Page History

...

AMI Access Instructions

The only access to the Sparkplug SiteWise IoT Bridge system is via SSH. As part of of the EC2 instance provisioning process a 'keypair' is associated with the instance. This is something that available during the keypair creation process and can not be retrieved after the initial creation so make sure to save it. To access the instance, you will need the following pieces of information.

...

In addition to the above information, you must make sure the SSH port (22) is open for inbound connections in the security group you have associated with the Sparkplug SiteWise IoT Bridge EC2 instance you have created.

There is nothing unique about connecting to a Sparkplug SiteWise IoT Bridge instance over any other other AWS Ubuntu based instance. AWS provides detailed instructions on this process of connecting via SSH and SCP here if you are unfamiliar with it.

...

The following shows the files that are likely of most interest with regard to Sparkplug SiteWise IoT Bridge functionality.

@ This is the core configuration file where AWS SiteWise and MQTT Server configuration is performed - details can be found here:
# https://docs.chariot.io/display/CLD80/SSB%3AIB%3A+Configuration
/opt/ssbIB/conf/ssbIB.properties

# This is the log file directory. Cirrus Link support may ask for these files to resolve configuration, connectivity, or other
# issues.
/opt/ssbIB/log

# For support tickets and debugging purposes Cirrus Link support may ask you to make modifications to this file on occasion
/opt/ssbIB/conf/logback.xml

# This starts the Sparkplug SiteWiseIoT Bridge service - note the service starts automatically on boot so using this script directly
# is only generally needed for debugging
/opt/ssbIB/daemonStart.sh

# This stops the service
/opt/ssbIB/daemonStop.sh