Skip to main content
You install Gliss from one CloudFormation stack. These are the only values you provide; everything else is derived from them or has a default.
The Gliss console fills in the control plane endpoint, the single-use join token and the trust anchor (controlPlane.*) for you. You don’t type them.

Parameters at a glance

Fields

string
required
EKS cluster name and the cluster’s slug in every AWS name the platform derives, 2 to 17 lowercase letters or digits, starting with a letter. No hyphens: every derived name is gliss-<cluster>-…, so a hyphen would let one cluster’s name prefix (gliss-a-*) cover another cluster’s names (gliss-a-b-…) in IAM and bucket patterns. It must be unique among Gliss clusters in this AWS account, in every region. 17 characters is the most that leaves room in per-app names: buckets are gliss-<cluster>-<app>-<8 hex> (at most 63 characters) and roles gliss-<cluster>-<app>-preview (at most 64). Secrets live under gliss/<clusterName>/ in Secrets Manager.CloudFormation parameter: ClusterName.If refused: use 2 to 17 lowercase letters or digits, starting with a letter, with no hyphens.
object
required
The domain apps are published under. Live apps get <name>.<domain>, Beta *.beta.<domain>, Preview *.preview.<domain>, and the secret-intake page secrets.<domain>.
object
required
internal | internet-facing
required
The load balancer’s scheme, fixed at install. internal is VPC only: only the VPC and networks routed to it (VPN, Direct Connect, transit gateway, Client VPN) reach the apps. internet-facing (the default) is reachable from the internet, limited by internetAccess: Allowlist by default, Public only with approval.Default: "internet-facing". CloudFormation parameter: IngressExposure.
allowlist | public
With an internet-facing load balancer: allowlist (only allowedCidrs and the VPC may connect) or public (anyone). An install is always allowlist: public is refused here and reached later only through approve-change-set.sh --approve-public, with the Gliss organisation admin’s signed approval.Default: "allowlist". CloudFormation parameter: InternetAccess.
string[]
Required with an internet-facing load balancer and internetAccess allowlist: the public IPv4 ranges that may connect, such as your VPN’s or office’s egress addresses. One to 25, each /16 or narrower, written as the range’s first address, never a private or reserved range. IPv4 only: the load balancer and the VPC are IPv4. Changed later in place, as an IT-approved change (approve-change-set.sh --set-parameter AllowedCidrs=…).At most 25 items. CloudFormation parameter: AllowedCidrs.If refused: the public egress addresses of your VPN or office, such as 198.51.100.7/32.
string
Never set at install: approve-change-set.sh --approve-public sets it, to the digest of the Gliss organisation admin’s signed approval of public access.CloudFormation parameter: PublicExposureApproval.
object
required
The on-demand node group that runs Live apps and the platform. Preview and Beta run on a separate spot pool that is derived from this.
object
required
The control plane this cluster joins, and the trust anchor for everything it signs. The console fills every field in from the Launch Stack link; IT does not type the keys.
internal | with-apps
Who can reach the secret-intake page at secrets.<domain>: internal (the VPC only, on its own internal load balancer when the main one is internet-facing) or with-apps (whoever reaches the apps: the allowlist, or anyone when the cluster is public). Required when ingressExposure is internet-facing; left out on an internal install, it is internal.CloudFormation parameter: SecretIntakeExposure.
integer
How long logs, maintenance-bot transcripts and the trail’s audit logs are kept in the Gliss bucket in this account. Default and minimum 30 days.From 30 to 3650. Default: 30. CloudFormation parameter: LogRetentionDays.
string
IT’s maintenance window, in UTC: <day>@<HH:MM>/<hours>h, where day is mon to sun, or daily; from 1 to 23 hours. EKS Auto Mode replaces nodes on AWS’s schedule (a new node image about once a week); the Gliss NodePools’ disruption budgets hold that, and consolidation, to this window. Platform releases that apply automatically will use it too.Default: "sun@02:00/4h". CloudFormation parameter: MaintenanceWindow.If refused: use a window such as sun@02:00/4h (Sunday 02:00 to 06:00 UTC) or daily@03:00/2h.
object
Who besides the Gliss agent may change what Gliss manages in the cluster. Both fields are defaulted; IT changes them only to name its own break-glass group.