Skip to main content

Chef Ohai

Integrate Chef Ohai with Cloudaware to ingest detailed AWS EC2 instance facts into the CMDB for richer inventory, troubleshooting, and governance.

info
  • Audience: Cloudaware administrators, DevOps/platform engineers
  • Outcome: The Chef Ohai integration is configured, and AWS EC2 instance facts are available in the Cloudaware CMDB for inventory, troubleshooting, and governance

Capabilities​

The integration supports:

  • Ingestion of AWS EC2 instance facts collected by Chef Ohai from an S3 bucket
  • Enrichment of AWS EC2 records in the Cloudaware CMDB with detailed system properties
  • Inventory, troubleshooting, and governance workflows based on Chef-derived metadata

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).
  • Chef Ohai configured to generate facts for AWS EC2 instances.
  • AWS EC2 instance facts uploaded to an AWS S3 bucket accessible by Cloudaware.
  • AWS account connected to Cloudaware.
note

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

Add a Chef Ohai Integration to Cloudaware​

To connect Chef Ohai data to Cloudaware:

  1. In Cloudaware, go to Admin.
  2. Find Chef Ohai, then click + ADD.
  3. Enter the following values:
    • AWS Account: Select the AWS account from the drop-down list that owns the S3 bucket.
    • 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 where Cloudaware should read the uploaded facts.
  4. Click SAVE.
  5. Confirm that the integration status indicator is green.

View Chef Ohai Data in CMDB​

To browse Chef Ohai facts on AWS EC2 instance records:

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

Supported Objects​

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

Cloudaware ObjectChef Ohai Data
AWS EC2 InstanceChef Ohai facts collected from the S3 bucket

Troubleshooting​

note

Initial data collection may take time to complete.

No Chef Ohai Facts Appear in CMDB​

  • Allow the initial discovery cycle to complete.
  • Confirm that the AWS account is connected to Cloudaware.
  • Confirm that the S3 bucket name, bucket region, and file prefix are correct.
  • Verify that Chef Ohai fact files exist in the configured S3 bucket path.
  • In CMDB Navigator, verify that you are viewing the related AWS EC2 instance records.

Integration Shows Red Status​

  • Confirm that Cloudaware has access to the selected AWS account and S3 bucket.
  • Check whether the configured bucket region matches the actual S3 bucket region.
  • Verify that the file prefix points to the path where Chef Ohai facts are uploaded.
  • Re-enter the integration details by editing the integration in Cloudaware.

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 Chef Ohai.
  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 Chef Ohai.
  3. Select the specific integration.
  4. Open the three-dot menu (⋮), then click Delete.
  5. Confirm the deletion if prompted.

Security Notes​

  • Store Chef Ohai fact files in a dedicated S3 bucket or prefix used only for Cloudaware ingestion.
  • Grant Cloudaware the minimum required S3 read access to the bucket and prefix that contain Chef Ohai facts.
  • Avoid uploading secrets, tokens, private keys, or other sensitive runtime data in Chef Ohai fact files.
  • Review bucket access policies periodically to confirm that only approved principals can read or write the fact files.
  • Remove stale fact files according to your organization's data-retention policy.