Organizations migrating to the Chef 360 Platform often have existing operational processes built around Chef Automate, including: 

• Chef Infra Client run history dashboards 

• Compliance reporting 

• Audit workflows 

• Operational troubleshooting and reporting 

The Chef Automate Connector preserves these workflows by forwarding supported run and compliance data from Chef 360-managed infrastructure to Chef Automate. 

How the Connector Works: 

The Chef Automate Connector integrates Chef 360 with an existing Chef Automate deployment by forwarding Chef Infra Client run data and supported compliance information to the configured Chef Automate Data Collector endpoint. 

Once configured: 

• A Chef Infra Client run executes on a managed node. 

• Chef 360 processes the run information. 

• The connector forwards the supported data to the configured Chef Automate Data Collector endpoint. 

• The forwarded data becomes available through the existing Chef Automate dashboards and reporting interfaces. 

The connector is configured once per tenant and applies across organizations within that tenant. 

To configure the integration: 

• Sign in to the Chef 360 Platform. 

• Navigate to Tenant Management → Automate Connector. 

• Enter the Chef Automate Data Collector URL in the following format: 

           https://<automate-host>/data-collector/v0/ 

• Generate or obtain an API token from Chef Automate by navigating to: 

           Settings → API Tokens 

• Paste the API token into the connector configuration. 

• Configure SSL verification settings as appropriate for your environment. 

• Save the configuration. 

After the connector is enabled, Chef 360 begins forwarding supported Chef Infra Client run data and compliance information to the configured Chef Automate instance. 

Verifying the Integration: 

After configuring the connector: 

• Upload a cookbook to Chef 360 Declarative State Management (DSM). 

• Bootstrap or manage a node with Chef 360. 

• Assign a run list or policy as required. 

• Execute a Chef Infra Client run on the node. 

• Open Chef Automate → Infrastructure → Client Runs and verify that the run information appears for the managed node. 

Successful visibility in Chef Automate confirms that the connector is forwarding supported data correctly. 

Connector Behavior During Connectivity Issues: 

The Chef Automate Connector is designed to tolerate temporary connectivity interruptions. 

Temporary outages: 

Chef 360 stores incoming run reports and retries delivery automatically. Once connectivity is restored, queued reports are forwarded without requiring manual intervention. 

 Extended outages: 

For prolonged outages, the connector automatically disables itself to prevent indefinite retry behavior. After the Chef Automate environment becomes available again, a tenant administrator can re-enable the connector through: 

Tenant Management → Automate Connector 

Once re-enabled, forwarding resumes for subsequent Chef Infra Client runs. 

Benefits: 

Using the Chef Automate Connector allows organizations to: 

• Continue using existing Chef Automate dashboards and reporting. 

• Preserve established operational and audit workflows while adopting Chef 360. 

• Integrate Chef 360-managed infrastructure with existing Chef Automate visibility. 

• Reduce operational changes during platform migration by maintaining familiar reporting interfaces. 

Additional Information: 

The Chef Automate Connector Complements Chef 360 Declarative State Management (DSM). 

• DSM manages infrastructure configuration by allowing organizations to define desired state using Chef Infra cookbooks and policies. 

• Chef Automate provides centralized visibility into Chef Infra Client runs and supported compliance information through dashboards and reporting. 

• The Chef Automate Connector bridges these capabilities by forwarding supported data from Chef 360-managed nodes to an existing Chef Automate instance.