How-To: Create Your First EZSSH Policy

Learn what EZSSH policies are, how Hybrid Policies and Azure Policies differ, and which one to create first for your multi-cloud, on-premises, and Azure SSH endpoints.

Overview - What Are EZSSH Policies?

EZSSH makes it easy to manage access to your SSH endpoints. Your users authenticate with their corporate identity, and EZSSH creates a short-lived SSH certificate and connects them to the endpoint, with no agent on the endpoint and no keys for the user to manage. To do this, EZSSH needs to know who in your organization has access to each endpoint. That is what policies are for.

A policy contains:

  • Endpoints: The servers the policy gives access to.
  • Owners: The people who can make changes to the policy.
  • Access policies: One or more sets of rules that define which Linux principals can be used, for how long, who is approved automatically, who needs someone else to approve their request, and who can approve requests.

EZSSH offers two types of policies, and you can use both in the same subscription: Hybrid Policies and Azure Policies. The main difference is that an Azure Policy is assigned an Azure scope, so it can automatically detect new Azure VMs in that scope and add them to the policy.

Which EZSSH Policy Type Should I Use?

What You Want to Access What to Create Guide
On-premises servers, or VMs in AWS, Google Cloud, or any other cloud Hybrid Policy. You list each endpoint by IP address or FQDN, make the endpoints trust the policy’s SSH CA with a cloud-init file or bash script, and grant access to Entra ID users, groups, and service principals. Create a Hybrid Policy
Azure VMs, where you want EZSSH to detect new VMs and use your Azure roles Azure Policy. You pick an Azure subscription or resource group, and EZSSH detects the VMs in it and can set them up for you. You can grant access to Entra ID objects and to Azure RBAC roles, such as everyone who is an Owner of the VM. Create an Azure Policy
Your GitHub organization No policy needed. Once your administrator has set up SSH certificates in GitHub, your engineers can go straight to elevating into GitHub with ezssh git. Access GitHub with EZSSH

What Is the Difference Between Hybrid Policies and Azure Policies?

Hybrid Policy Azure Policy
Best for On-premises servers and VMs in any cloud Azure VMs
How endpoints are added You add each endpoint by IP address or FQDN EZSSH detects the VMs in the Azure subscription or resource group
How endpoints trust the policy’s SSH CA You run a cloud-init file or bash script EZSSH can add it for you, or you run a cloud-init file or bash script
Who can be given access Entra ID users, groups, and service principals Entra ID users, groups, and service principals, plus Azure RBAC roles
Access EZSSH needs in Azure None Reader or Contributor on the scope

What Are EZSSH Hybrid Policies?

Hybrid Policies are great for all your endpoints that are not in Azure. You manually add the endpoints that the policy gives access to, and EZSSH gives you a cloud-init file to set up new cloud endpoints, or a bash script to run on existing endpoints, so they trust the policy’s CA as an SSH certificate issuer. You give access to Entra ID users, groups, and service principals by adding them to the policy.

🚀 Create a Hybrid Policy

What Are EZSSH Azure Policies?

Azure Policies require EZSSH to have access to your Azure subscription or resource group. In return, EZSSH automatically detects the endpoints in the scope and adds them to the policy. It can also add the policy’s certificate to your Azure VMs for you.

Azure Policies offer the same access management as Hybrid Policies. However, we understand that many organizations already manage access to their Azure resources with tools such as Microsoft Entra Privileged Identity Management (PIM). That is why Azure Policies can also grant access based on the Azure RBAC roles assigned on the resource, so Azure and EZSSH access management work together.

🚀 Create an Azure Policy