Session identity
A launcher can name the cloud identity its session VM runs as. The default leaves the VM on the environment’s usual identity: Google Cloud’s default service account, and no instance profile on AWS.
This setting is for system admins on AWS and Google Cloud. It is hidden on Kubernetes. Screenshots of the field wait for an image rebake; the control is in the product now.
Where it is set
Section titled “Where it is set”On New App or App Settings, open Advanced. It is shown only to a system admin. Session VM identity lists Default and the allowlisted identities. When the environment has no allowlist yet, the control is disabled and says no session identities are configured, and where to add them. On Kubernetes it is disabled and says it is not available. Everyone else sees nothing.
Google Cloud
public/screenshots/session-identity/session-identity-step1.gcp.pngAWS
public/screenshots/session-identity/session-identity-step1.aws.png- Google Cloud: a service account email. The session template runs as that account.
- AWS: an instance profile name or ARN.
From the login node, a system admin can set it when creating a launcher:
eureka launcher add --app Desktop --project NAME --instance-type TYPE --session-identity IDENTITYThere is no MCP argument for it. launcher_add always uses the default identity.
Allowlist
Section titled “Allowlist”Each environment lists the identities a launcher may use as session_identities on the compute provider (a list, or comma-separated text). An empty or missing list turns the feature off. Advanced then shows the control disabled, with a hint, to a system admin.
The server checks every save and every launch:
- Only a system admin may set or change the identity, and the value must be on the allowlist.
- A non-admin who saves a launcher can keep the stored value when it is still allowlisted. They cannot pick a new one.
- Removing an identity from the list blocks new sessions from launchers that still name it.
What the identity can do
Section titled “What the identity can do”Anyone with a shell on the session VM can use that identity through the instance metadata service for as long as its grants are live. That includes every user of a shared desktop and any process they run. Treat the setting as giving those permissions to everyone who can open the launcher.
Keep the target identity narrow. To revoke it, remove the cloud grants or remove the allowlist entry.
The environment’s own identity must be allowed to start a VM as that target:
- Google Cloud:
iam.serviceAccounts.actAson each target service account, not on the whole project. - AWS:
iam:PassRoleon each target role, and only when the service is EC2.
The environment can also be launched on an identity an admin already created, instead of one Eureka creates. That identity needs the permissions a normal environment identity has, plus the grants above. Unset, Eureka creates its own.