Deploying Galileo - EKS

Get your Kubernetes cluster up and running while setting up IAM and Trust Policies and the 4 Galileo DNS endpoints. The Galileo applications run on managed Kubernetes environments like EKS and GKE, but this document will specifically cover the configuration and deployment of an EKS environment.
⏱ Total time for deployment: 30-45 minutes
This deployment requires the use of AWS CLI commands. If you only have cloud console access, follow the optional instructions below to get eksctl working with AWS CloudShell.

Step 0: (Optional) Deploying via AWS CloudShell

To use eksctl via CloudShell in the AWS console, open a CloudShell session and do the following:
# Create directory
mkdir -p $HOME/.local/bin
cd $HOME/.local/bin
# eksctl
curl --silent --location "$(uname -s)_amd64.tar.gz" | tar xz -C /tmp
sudo mv /tmp/eksctl $HOME/.local/bin
The rest of the installation deployment can now be run from the CloudShell session. You can use vim to create/edit the required yaml and json files within the shell session.
Galileo recommends the following Kubernetes deployment configuration:
Recommended Value
Nodes in the cluster’s core nodegroup
4 (min) 5 (max) 4 (desired)
CPU per core node
RAM per core node
16 GiB RAM
Number of nodes in the cluster’s runners nodegroup
1 (min) 5 (max) 1 (desired)
CPU per runner node
RAM per runner node
32 GiB RAM
Minimum volume size per node
200 GiB
Required Kubernetes API version
Storage class

Step 1: Creating Roles and Policies for the Cluster

  • Galileo IAM Policy: This policy is attached to the Galileo IAM Role. Add the following to a file called galileo-policy.json
"Version": "2012-10-17",
"Statement": [
"Effect": "Allow",
"Action": [
"Resource": "arn:aws:eks:CLUSTER_REGION:ACCOUNT_ID:cluster/CLUSTER_NAME"
  • Galileo IAM Trust Policy: This trust policy enables an external Galileo user to assume your Galileo IAM Role to deploy changes to your cluster securely. Add the following to a file called galileo-trust-policy.json
"Version": "2012-10-17",
"Statement": [
"Effect": "Allow",
"Principal": {
"AWS": [
"Service": ""
"Action": "sts:AssumeRole"
  • Galileo IAM Role with Policy: Role should only include the Galileo IAM Policy mentioned in this table. Create a file called, make it executable with chmod +x and run it. Make sure to run in the same directory as the json files created in the above steps.
#!/bin/sh -ex
aws iam create-policy --policy-name Galileo --policy-document file://galileo-policy.json
aws iam create-role --role-name Galileo --assume-role-policy-document file://galileo-trust-policy.json
aws iam attach-role-policy --role-name Galileo --policy-arn $(aws iam list-policies | jq -r '.Policies[] | select (.PolicyName == "Galileo") | .Arn')

Step 2: Deploying the EKS Cluster

With the role and policies created, the cluster itself can be deployed in a single command using eksctl. Using the cluster template here, create a galileo-cluster.yaml file and edit the contents to replace CUSTOMER_NAME with your company name like galileo. Also check and update all availabilityZones as appropriate.
With the yaml file saved, run the following command to deploy the cluster:
eksctl create cluster -f galileo-cluster.yaml

Step 3: EKS IAM Identity Mapping

This ensures that only users who have access to this role can deploy changes to the cluster. Account owners can also make changes. This is easy to do with eksctl with the following command:
eksctl create iamidentitymapping
--cluster customer-cluster
--region your-region-id
--arn "arn:aws:iam::CUSTOMER-ACCOUNT-ID:role/Galileo"
--username galileo
--group system:masters
NOTE for the user: For connected clusters, Galileo will apply changes from github actions. So should be allow-listed for your cluster’s ingress rules if you have any specific network requirements.

Step 4: Required Configuration Values

Customer specific cluster values (e.g. domain name, slack channel for notifications etc) will be placed in a base64 encoded string, stored as a secret in GitHub that Galileo’s deployment automation will read in and use when templating a cluster’s resource files.\
Mandatory Field
AWS Account ID
The Customer's AWS Account ID that the customer will use for provisioning Galileo
Galileo IAM Role Name
The AWS IAM Role name the customer has created for the galileo deployment account to assume.
EKS Cluster Name
The EKS cluster name that Galileo will deploy the platform to.
Domain Name
The customer wishes to deploy the cluster under e.g.
Root subdomain
e.g. "galileo" as in
Trusted SSL Certificates (Optional)
By default, Galileo provisions Let’s Encrypt certificates. But if you wish to use your own trusted SSL certificates, you should submit a base64 encoded string of
  1. 1.
    the full certificate chain, and
  2. 2.
    another, separate base64 encoded string of the signing key.
AWS Access Key ID and Secret Access Key for Internal S3 Uploads (Optional)
If you would like to export data into an s3 bucket of your choice. Please let us know the access key and secret key of the account that can make those upload calls.
NOTE for the user: Let Galileo know if you’d like to use LetsEncrypt or your own certificate before deployment.

Step 5: Access to Deployment Logs

As a customer, you have full access to the deployment logs in Google Cloud Storage. You (customer) are able to view all configuration there. A customer email address must be provided to have access to this log.

Step 6: Customer DNS Configuration

Galileo has 4 main URLs (shown below). In order to make the URLs accessible across the company, you have to set the following DNS addresses in your DNS provider after the platform is deployed.
⏱ Time taken : 5-10 minutes (post the ingress endpoint / load balancer provisioning)
Each URL must be entered as a CNAME record into your DNS management system as the ELB address. You can find this address by listing the kubernetes ingresses that the platform has provisioned.

Step 7: Post-deployment health-checks