Connector
Connections across Solarius products and services. Connect infrastructure and security, share selected resource context, and follow related work across product boundaries.
Connect your products
Build customer integrations
Operate with clear boundaries
Connector links Solarius products and services so they can exchange selected information and associate records for the same workload. You can connect Infra resources to Guard assets, bring security context into infrastructure work, and follow related operations across products.
Each product keeps ownership of its resources, permissions, and execution. A connection determines which information crosses the product boundary; the receiving product determines who can use that information.
A shared view of your services
An Infra load balancer, its Guard service asset, and a Guard incident can refer to the same application. Connector records those relationships using resource IDs, so a rename does not separate the infrastructure from its security history.
Infra shares selected inventory and operational state through Connector with mapped Guard assets. Approved grants and resource mappings limit the exchange.
Start with one connection
Connect Infra and Guard walks through approvals, scope selection, and the first synchronization. Start with one project and one asset group before expanding the connection.
The connection model explains ownership and deployment boundaries. Supported services lists product connections and service-specific enrollment, including the Status general-availability boundary.
Build a customer integration
Connect your service catalog, deployment system, or ticket application through the Connector API. A custom integration registration supplies its identity; directional grants select the Solarius context it can read and the external summaries it can publish.
Synchronize a service catalog provides a downloadable worker that commits complete inventory snapshots. Receive Connector events provides a signed webhook receiver with durable admission and deduplication. Use Publish external context to associate a deployment or ticket with a mapped native resource.
Connect context to an operating task
Choose a guide for the result you need:
| Goal | Guide |
|---|---|
| Associate infrastructure with security inventory | Map resources across products |
| Select information and understand freshness | Data sharing and synchronization |
| Protect an application running on Infra | Protect an Infra service with Guard |
| Review who can approve and use a connection | Access and approvals |
| Rotate credentials or retire a connection | Manage a connection |
| Recover missing or stale information | Troubleshoot Connector |
| Share one project's inventory and selected labels | Share an Infra project with Guard |
| Bring findings into infrastructure work | Return Guard security context to Infra |
| Add another project without replacing the connection | Add a project to a connection |