Hyphen

Connection Types

Explore the different connection types in Hyphen that link platform resources to external cloud providers, code repositories, registries, and observability platforms.

A connection links a Hyphen resource to a resource in an external service. Each integration supports a specific set of connection types.

See Integrations Overview for the available integrations and the types that each supports.

The connection type determines which resource Hyphen connects and how Hyphen uses it. The same type can refer to different resources in different services.

Table of Contents

Collaboration and Source Code

Connection type What it connects Supported integrations
Distribution List A Hyphen organization, team, project, project environment, or app connects to a group with an email address. Google Workspace: Google Group. Microsoft Office 365: Microsoft 365 group.
Channel A Hyphen team connects to a conversation channel. Slack: Slack channel. Microsoft Teams: channel within a Microsoft team.
Code Repository A Hyphen project, app, or Kubernetes cluster connects to a source repository. A connection alone does not start a deployment. GitHub.

Cloud Organization and Build Artifacts

Connection type Purpose Supported integrations and resources
Folder Organize the cloud resources for a Hyphen project. AWS: organizational unit. Google Cloud: folder.
Cloud Workspace Provide the cloud resource scope for a project or project environment. AWS: account. Azure: resource group. Google Cloud: project.
Container Registry Store container images for a Hyphen project. AWS: ECR. Azure: Container Registry. Google Cloud: Artifact Registry. Docker Hub: repository.
Proxy Container Registry Provide a registry proxy for a project environment. Google Cloud.
Site Registry Store static site builds for a Hyphen project. Cloudflare.
Static Site Connect a static site deployment to its hosted site and URL. Cloudflare.

Container Registry stores container images. Site Registry stores static site builds. Static Site represents the hosted site that serves a deployment.

See Builds for container images and Deployment Previews for preview deployments.

Deployment Infrastructure

Hyphen can prepare these connections as part of a deployment. You do not need to add each infrastructure connection manually.

Connection type Purpose Supported integrations
Network Group Provide network resources for an environment or region. AWS, Azure, Google Cloud.
Cloud Native Container Run an app deployment instance as a container service. AWS: ECS. Azure: Container Apps. Google Cloud: Cloud Run.
DNS Zone Connect a Hyphen zone to a provider DNS zone. AWS, Azure, Google Cloud, Cloudflare.
DNS Record Connect a resource record or value to a provider DNS record. AWS, Azure, Google Cloud, Cloudflare.
Load Balancer Route traffic through an environment ingress. AWS, Azure, Google Cloud, Cloudflare.
Backend Pool Group the backends for an app deployment. AWS, Azure, Google Cloud, Cloudflare.
Backend Endpoint Connect an ingress or app deployment instance to a traffic destination. AWS, Azure, Google Cloud, Cloudflare.
Custom Domain Connect a domain and its HTTPS configuration to an environment ingress. AWS, Azure, Google Cloud.
Object Storage Connect environment storage to a provider bucket or container. AWS: S3. Azure: Blob Storage. Google Cloud: Cloud Storage.

See Deploy Quickstart and Storage for deployment requirements and storage configuration.

Telemetry and Managed Kubernetes

Connection type Purpose Supported integrations
APM Map a Hyphen app to existing application names or services so Agent can read logs for a selected environment. New Relic, Datadog, SigNoz.
Kubernetes Observability Link a registered Kubernetes cluster to its runtime metrics and logs. AWS, Azure, Google Cloud, New Relic, Datadog, SigNoz.
Managed Kubernetes Cluster Link a registered cluster to its existing managed cloud cluster. This connection does not create a cluster. AWS: EKS. Azure: AKS. Google Cloud: GKE.

APM supports two modes:

  • Shared by environment attribute: All environments use one application or service name. An attribute separates their logs.
  • Per environment: Each project environment maps to a separate application or service name.

Kubernetes Observability and Managed Kubernetes Cluster serve different purposes. Observability supplies telemetry; the managed cluster connection identifies the cluster in its cloud provider.

AWS uses the EKS cluster ARN. Azure uses the AKS resource ID. Google Cloud uses the full GKE resource name.

The cloud integrations use CloudWatch, Azure Monitor, or Google Cloud telemetry. New Relic, Datadog, and SigNoz use their own cluster identifiers.

These connections require an existing cluster and the required provider permissions. Telemetry connections also require data collection in the provider.

See Log Analysis and Kubernetes Observability for telemetry configuration.