Skip to content

Deploying the SenseOn Universal Sensor on AWS EC2

This guide tells you how to deploy the SenseOn Universal Sensor on an EC2 instance in AWS. The sensor gives visibility into host activity, Docker containers, and Kubernetes workloads (for example, EKS).


Prerequisites

💡 Install command: The install command and the installer key for your tenant are available from Settings > Universal Sensor in the SenseOn platform.

  • A SenseOn account with access to Settings > Universal Sensor (to get your install command and installer key)
  • AWS permissions to:
  • Launch and manage EC2 instances
  • Connect through EC2 Instance Connect or Systems Manager (SSM)
  • Manage EKS clusters and EC2 node groups
  • A supported EC2 AMI (for example, Amazon Linux 2, Ubuntu 20.04+, RHEL 7+)
  • Outbound HTTPS access from the EC2 instance to the SenseOn domain of your tenant

Option A: Install at Launch via User Data

For new instances, the simplest deployment procedure is to put the SenseOn install command in the instance user data. The agent installs automatically when the instance boots for the first time.

  1. Go to AWS Console > EC2 > Launch Instance.
  2. Configure your AMI, instance type, key pair, networking and IAM role as usual.
  3. Expand Advanced details.
  4. Paste the script that follows into User data. Replace the placeholders with your tenant hostname and installer key:

    #!/bin/bash
    curl -fsSL https://<your-tenant>.senseon.io/install.sh \
      | SENSEON_INSTALLER_KEY="<your-installer-key>" bash
    
  5. Launch the instance.

The Universal Sensor installs during the first boot. Make sure that the host shows in Assets > Devices in a few minutes.

💡 Auto Scaling groups: Add the same user data block to your launch template. Then each scaled-out instance installs the sensor automatically.


Option B: Install on a Running Instance

For instances that already run:

  1. Connect to the instance through EC2 Instance Connect, AWS Systems Manager Session Manager, or SSH.
  2. Run the install command that you copied from Settings > Universal Sensor:

    curl -fsSL https://<your-tenant>.senseon.io/install.sh \
      | sudo SENSEON_INSTALLER_KEY="<your-installer-key>" bash
    

The installer detects if the host uses apt or rpm. Then it installs the applicable package.

🛡 Optional: Verify the install script checksum

Your security policy can make a checksum check mandatory before you run remote scripts. If so, download the script first. Then do a check of the checksum. Then run the script:

# Step 1: Download the script
curl -fsSL https://<your-tenant>.senseon.io/install.sh -o install.sh
# Step 2: Verify the checksum (compare against the value shown in Settings > Universal Sensor)
sha256sum install.sh
# Step 3: Run the script
sudo SENSEON_INSTALLER_KEY="<your-installer-key>" bash install.sh

Option C: Install via Systems Manager (Run Command)

To deploy to existing instances across a fleet:

  1. In AWS Systems Manager, open Run Command.
  2. Select the AWS-RunShellScript document.
  3. Set the command to:

    curl -fsSL https://<your-tenant>.senseon.io/install.sh \
      | SENSEON_INSTALLER_KEY="<your-installer-key>" bash
    
  4. Select your target instances (by tag, resource group, or instance IDs).

  5. Run the command.

SSM reports the status of each instance when the installation completes on each host.


Verify in the SenseOn Portal

  1. Log in to the SenseOn web portal.
  2. Go to Assets > Devices.
  3. Look for the new EC2 host or hosts with a recent Last Seen timestamp.

Additional Notes

  • You must install the Universal Sensor on the host OS so that it observes containers and pods correctly.
  • In EKS or ECS environments, deploy the sensor directly on EC2 nodes. Do not deploy it in a pod or container.
  • The host must have outbound HTTPS access to the SenseOn domain of your tenant. If you have a strict egress policy, add *.senseon.io and *.snson.net to the allowlist.
  • To see the agent status, use systemctl status senseon-seed.service.

Troubleshooting

Install command fails to download the script

  • Make sure that the instance has outbound HTTPS access to the SenseOn domain of your tenant.
  • If you use TLS interception, make sure that *.snson.net and *.senseon.io are excluded.

Agent not reporting

  • Make sure that the host shows in Assets > Devices.
  • Examine the service status:

    sudo systemctl status senseon-seed.service
    
  • If the steps before this one do not correct the problem, restart the service or reboot the instance.

  • For more help, refer to Troubleshooting or contact support@senseon.io.