Skip to main content

Nagios

Integrate Nagios with Cloudaware to surface EC2 instance facts and monitoring details for AWS fleets.

info
  • Audience: Cloudaware administrators, monitoring teams, and cloud operations teams
  • Outcome: Nagios-exported EC2 instance facts are imported from S3 and available on AWS records in CMDB for inventory review, reporting, and operational context

Capabilities​

The integration supports:

  • EC2 instance facts exported by Nagios available in Cloudaware CMDB.
  • Nagios monitoring details connected to AWS instance records for operational review.
  • CMDB list views and reports that include Nagios-derived facts for AWS fleet analysis.
warning

Although Nagios is a multi-cloud monitoring solution, the Cloudaware integration currently supports only AWS.

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).
  • An AWS account connected to Cloudaware.
  • EC2 instance facts exported by Nagios to an AWS S3 bucket accessible by Cloudaware.
  • The AWS account, bucket name, bucket region, and file prefix for the uploaded Nagios facts.

Add Nagios Integration Details​

  1. In Cloudaware, go to Admin.
  2. Find Nagios, then click + ADD.
  3. Enter the following values:
    • AWS Account: Select the AWS account from the drop-down list.
    • Bucket Name: Enter the name of the S3 bucket that stores the uploaded EC2 instance facts.
    • Bucket Region: Specify the AWS region where the S3 bucket resides.
    • File Prefix: Enter the path prefix within the bucket for Cloudaware to read the uploaded facts.
  4. Click Save.
  5. Confirm that the integration status indicator is green.

View Nagios Data in CMDB​

  • Open an AWS object record to view the relevant section (e.g. AWS EC2 Instance Facts (Ansible Fact)) in the RELATED CIs tab.
  • Build a custom list view for the AWS object to view updates.
  • Build a report on the AWS object.

Troubleshooting​

note

Initial data collection may take time to complete after Nagios facts are uploaded to S3.

Integration Shows Red Status​

  • Verify that the AWS account, bucket name, bucket region, and file prefix are configured correctly.
  • Confirm that Cloudaware can access the S3 bucket that stores the Nagios fact files.
  • Check that the bucket region matches the region selected in the integration settings.
  • Re-enter the integration details by editing the integration in Cloudaware.

Nagios Facts Are Missing from CMDB​

  • Confirm that the expected EC2 instance fact files are available in the configured S3 bucket and prefix.
  • Verify that the files are exported in the expected location before the Cloudaware collection cycle starts.
  • Allow time for Cloudaware to process the imported data.
  • Using CMDB Navigator, open AWS EC2 instance records to view related section on CIs

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

Reconfigure or Remove the Integration​

warning

To update bucket settings, edit the existing integration instead of deleting and re-creating it.

Update the Integration Details​

  1. Go to Admin.
  2. Select Nagios.
  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 Nagios.
  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 S3 permissions required to read the bucket and prefix that contain Nagios fact exports.
  • Store Nagios exports in a dedicated S3 prefix to limit the data available to the integration.
  • Avoid storing credentials, secrets, or sensitive configuration values in exported Nagios fact files.
  • Restrict S3 bucket access with least-privilege IAM policies and review access regularly.
  • Rotate any AWS access credentials used for the integration according to your organization's credential-rotation policy.
  • Update the Cloudaware integration immediately if bucket access, IAM permissions, or file locations change.