Cortex Service Descriptions
The table below describes the services that make up a Cortex deployment.
| Service | Description |
|---|---|
| cortex-accounts | Manages secrets, roles/grants, service users and accounts, and docker registry authorization |
| cortex-api | Manages graphql apis for Campaign development |
| cortex-auth | Manages single sign-on to Cortex |
| cortex-catalog | Registry for agents, skills, types, connections, Data Sources, profiles, and campaigns. |
| cortex-connections | Stores custom data connections and Fabric managed content configuration parameters and properties |
| cortex-console | Manages SENSA Fabric Console functionality |
| cortex-models | Stores and manages models, model experiments, and experiment runs in Fabric |
| cortex-operator | Cortex runtime and deployment, includes skills, agents, actions |
| cortex-processor-gateway | Orchestrates actions at runtime |
| dex | An identity service provider used by the cortex-auth service to map user identities and group associations from a system of record to Fabric roles. |
| mongodb | A noSQL database used by Cortex services; Mongo provides a persistent data store, Cortex Catalog, where the information and metadata pertaining to resource definitions (Agents, Skills, Campaigns, and Missions) is stored. |
| redis | A distributed in-memory key-value database. In Fabric Redis is used as a caching layer that stores short term runtime data; it serves as a quick lookup for Cortex job statuses, handler for agent invocation states, manager of sessions, and handler for authorization policies data. |
| s3-compatible-object-store | Provides object storage for Fabric managed content for the connections service; Minio is configured by default. |