An integration connects your Hyphen organization to an external service. A connection links a specific Hyphen resource to a resource in that service.
For example, an AWS integration authorizes access to your AWS organization. Its Cloud Workspace connections link project environments to AWS accounts.
One integration can support several connection types. See Connection Types for their purposes, provider resources, and requirements.
Table of Contents
Available Integrations
The tables below list the available integrations and their current connection types. Some features depend on the features enabled for your organization.
Cloud Infrastructure and Hosting
| Integration | Purpose | Supported connections |
|---|---|---|
| Amazon Web Services (AWS) | Connect AWS accounts, infrastructure, and EKS telemetry. | Folder, Cloud Workspace, Container Registry, Network Group, Cloud Native Container, DNS Zone, DNS Record, Load Balancer, Backend Pool, Backend Endpoint, Custom Domain, Object Storage, Managed Kubernetes Cluster, Kubernetes Observability. |
| Cloudflare | Connect static sites, DNS, and traffic routes. | Site Registry, Static Site, DNS Zone, DNS Record, Load Balancer, Backend Pool, Backend Endpoint. |
| Google Cloud | Connect Google Cloud projects, infrastructure, and GKE telemetry. | Folder, Cloud Workspace, Container Registry, Proxy Container Registry, Network Group, Cloud Native Container, DNS Zone, DNS Record, Load Balancer, Backend Pool, Backend Endpoint, Custom Domain, Object Storage, Managed Kubernetes Cluster, Kubernetes Observability. |
| Microsoft Azure | Connect Azure resource groups, infrastructure, and AKS telemetry. | Cloud Workspace, Container Registry, Network Group, Cloud Native Container, DNS Zone, DNS Record, Load Balancer, Backend Pool, Backend Endpoint, Custom Domain, Object Storage, Managed Kubernetes Cluster, Kubernetes Observability. |
Code and Container Images
| Integration | Purpose | Supported connections |
|---|---|---|
| Amazon Web Services (AWS) | Store container images in Amazon ECR. | Container Registry. |
| Docker Hub | Connect a container image repository. | Container Registry. |
| GitHub | Link source repositories to Hyphen projects, apps, or Kubernetes clusters. | Code Repository. |
| Google Cloud | Store container images in Artifact Registry and provide a registry proxy. | Container Registry, Proxy Container Registry. |
| Microsoft Azure | Store container images in Azure Container Registry. | Container Registry. |
Communication and Collaboration
| Integration | Purpose | Supported connections |
|---|---|---|
| Google Workspace | Connect Google Groups to Hyphen resources. | Distribution List. |
| Microsoft Office 365 | Connect Microsoft 365 groups to Hyphen resources. | Distribution List. |
| Microsoft Teams | Connect team channels in Microsoft Teams. | Channel. |
| Slack | Connect team channels and use Hyphen through Slack. | Channel. |
Application and Kubernetes Observability
| Integration | Purpose | Supported connections |
|---|---|---|
| Amazon Web Services (AWS) | Read EKS telemetry through CloudWatch. | Kubernetes Observability. |
| Datadog | Read application logs and Kubernetes telemetry. | APM, Kubernetes Observability. |
| Google Cloud | Read GKE telemetry through Google Cloud services. | Kubernetes Observability. |
| Microsoft Azure | Read AKS telemetry through Azure Monitor. | Kubernetes Observability. |
| New Relic | Read application logs and Kubernetes telemetry. | APM, Kubernetes Observability. |
| SigNoz | Read telemetry from SigNoz Cloud or your own SigNoz instance. | APM, Kubernetes Observability. |
Identity, Access, and Device Reports
Integrations can support reports in addition to their other connection types. Reports use the organization integration directly and do not require separate resource connections.
| Integration | Report data |
|---|---|
| GitHub | Access assignments for comparison with an identity directory. Device inventory reports are not supported. |
| Google Workspace | Identity and access data. Device inventory reports are not supported. |
| Microsoft Azure | Microsoft Entra ID identity, access, and device inventory data. |
| Microsoft Office 365 | Microsoft Entra ID identity, access, and device inventory data. |
| Mosyle Business | Apple device inventory. |
| Okta | Users, groups, applications, and access assignments. |
Reports read provider data. They do not create users, groups, or devices. Okta and Mosyle Business do not support separate resource connections.
Mosyle Manager for education is not supported.
Connect an Integration
- Open Integrations in your Hyphen organization.
- Select an integration.
- Complete its authorization or credential setup.
- Open the team, project, app, or cluster that needs a connection.
- Select the required connection type.
- Supply the provider resource identifier when required.
Some types can connect to existing resources or create new resources. Others require an existing resource, such as an APM application or managed Kubernetes cluster.
The provider guide describes the required input and any verification steps. A connection must reach Ready before Hyphen can use it.
Retired Integrations
Jira, npm, and incident.io are retired integrations. They are not available for new integration setup. Their guides remain as references for older configurations: