Skip to main content

Sensu

Integrate Sensu with Cloudaware to surface AWS EC2 Instance facts for cloud operations and inventory reporting.

info
  • Audience: Cloudaware administrators, cloud operations teams, and monitoring teams
  • Outcome: Sensu EC2 instance facts are available in CMDB for instance context, inventory review, and reporting

Capabilities​

The integration supports:

  • EC2 instance fact ingestion from Sensu exports stored in Amazon S3
  • Instance-level fact visibility in CMDB for AWS fleet inventory and operational context
  • Search and reporting for Sensu-provided EC2 instance facts using CMDB Navigator, CMDB list views, and reports

Prerequisites​

Before you begin, make sure you have:

  • Access to a Cloudaware account.
  • A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
  • Sensu EC2 instance facts exported to an Amazon S3 bucket accessible by Cloudaware.
  • AWS account, bucket name, region, and file prefix for the S3 location that stores the exported Sensu facts.
  • AWS account connected to Cloudaware.
note

Although Sensu supports multiple clouds, the Cloudaware integration currently supports only AWS.

Add a Sensu Integration to Cloudaware​

  1. In Cloudaware, go to Admin.
  2. Find Sensu, then click + ADD.
  3. Enter the following values:
    • AWS Account: Select AWS account that contains the S3 bucket with Sensu exports.
    • Bucket Name: The S3 bucket name.
    • Region: The AWS Region where the S3 bucket is located.
    • File Prefix: The S3 object prefix for the Sensu export files.
  4. Click Save.
  5. Confirm that the integration status indicator is green.
tip

Allow the initial discovery cycle to complete after enabling the integration.

View Sensu Data in CMDB​

  1. In Cloudaware, open CMDB Navigator.
  2. In the left pane, select AWS.
  3. Open AWS EC2 Instances and select an instance.
  4. Confirm that Sensu facts are displayed on the corresponding AWS EC2 instance in the Cloudaware CMDB.

Supported Objects​

Cloudaware surfaces Sensu-provided AWS EC2 instance facts on related CMDB records for inventory review and reporting.

CMDB ObjectSensu Data
AWS EC2 InstanceSensu facts collected from the S3 bucket

Troubleshooting​

note

Initial data collection may take time to complete.

Integration Shows Red Status​

  • Verify that the AWS account, bucket name, region, and file prefix are correct.
  • Confirm that the S3 bucket exists in the selected AWS Region.
  • Check that Cloudaware has permission to read the Sensu export files in the S3 bucket.

No Sensu Facts Appear in CMDB​

  • Confirm that Sensu export files are being written to the configured S3 location.
  • Verify that the file prefix matches the path where Sensu export files are stored.
  • Allow the next discovery cycle to process newly uploaded files.
  • In CMDB Navigator, verify that you are reviewing relevant AWS EC2 instance records.

Some Instance Facts Are Missing​

  • Confirm that the missing instances are included in the Sensu export files.
  • Check whether the exported facts contain identifiers that can be matched to AWS EC2 instance records in Cloudaware.
  • Review the export schedule to confirm that the S3 files include current Sensu data.

Still stuck? Contact Cloudaware Support at support@cloudaware.com with the integration name, S3 bucket details, and a brief description of the issue.

Reconfigure or Remove the Integration​

warning

To change the S3 source location, edit the existing integration instead of deleting and re-creating it.

Update the Integration Details​

  1. Go to Admin.
  2. Select Sensu.
  3. Select the specific integration.
  4. Open the three-dot menu (⋮), then click Edit.
  5. Update the required fields.
  6. Click Save.

Remove the Integration from Cloudaware​

  1. Go to Admin.
  2. Select Sensu.
  3. Select the specific integration.
  4. Open the three-dot menu (⋮), then click Delete.
  5. Confirm the deletion if prompted.

Security Notes​

  • Grant Cloudaware only the minimum S3 read permissions required to access the Sensu export location.
  • Scope access to the specific bucket and prefix used for Sensu export files whenever possible.
  • Review Sensu fact content before export, because instance facts may include hostnames, instance identifiers, configuration details, and other operational metadata.
  • Protect the S3 bucket with your organization's standard controls for encryption, access logging, retention, and public access blocking.
  • Rotate and review AWS access permissions according to your organization's credential and access review policies.