Oligo Security Runtime Sensor

This product is delivered as a preconfigured Amazon Machine Image (AMI) that deploys the Oligo Security Runtime Sensor on a Linux host.

The AMI includes all required Oligo sensor binaries and services. No inbound network access is required. Outbound HTTPS connectivity on TCP port 443 is required to allow the sensor to communicate with Oligo managed services.

Step 1. Launch the EC2 instance

Launch an EC2 instance using the Oligo Security Runtime Sensor AMI from AWS Marketplace.

A recommended instance type is preselected; customers may choose any supported instance type listed for this product.

No EC2 User Data is required for basic deployment.

Step 2. Required customer inputs and onboarding

No local license key or manual configuration is required on the instance at launch time.

After the instance is running, customers must complete onboarding with Oligo Security to associate the deployed sensor with the correct customer tenant and environment. Tenant assignment, activation, and policy configuration are performed remotely by Oligo after the sensor establishes an outbound connection.

Step 3. First boot behavior

When the EC2 instance boots:

1. The operating system initializes normally.
2. The Oligo sensor service starts automatically as a system service.
3. The sensor establishes a secure outbound connection to the Oligo cloud control plane.
4. Once connected, the sensor awaits tenant assignment and configuration from Oligo.

No manual steps are required on the instance during first boot.

Step 4. Verifying the sensor is running

Customers may optionally verify that the sensor is running by connecting to the instance and checking the service status:

sudo systemctl status oligo-sensor

The service should be shown as active and running.

Step 5. Configuration and updates

The Oligo sensor configuration is defined using a YAML configuration file. Configuration updates or sensor version updates can be applied using the native Oligo installer utility.

To update the sensor or apply configuration changes: sudo ./oligo-native-sensor-installer update sensor-values.yaml

Configuration updates can also be managed remotely by Oligo as part of normal operations.

Step 6. Automation and infrastructure as code

For large-scale or automated deployments, the Oligo sensor can be deployed using EC2 User Data, Terraform, or other automation tools. In these cases, the installer can be executed automatically during instance launch, and configuration values can be provided dynamically.

Step 7. Uninstalling the sensor

To remove the Oligo sensor from the instance, run: sudo ./oligo-native-sensor-installer uninstall

This removes the Oligo sensor binaries and services from the host.

Support and ongoing operations

After deployment, customers should contact Oligo Security support to complete onboarding, tenant association, policy configuration, and ongoing operational guidance.