Skip to main content

​
Prerequisites

  1. AWS Account: You need to have an AWS account to use AWS services, including CloudFormation.
  2. AWS EC2 Key Pair: Before creating the CloudFormation stack, you should have an EC2 Key Pair set up in your AWS account. If you don’t have one, you can follow the AWS documentation to create a key pair.
  3. Blink User: You must have either the Owner role,Contributor role, or a custom role that includes both the runners:view and runners:edit permissions. To learn more about role-based access and permissions, see the User Roles documentation.

​
Deployment Guide

Use CloudFormation as an option to deploy runners, if you don’t have Helm or a Host with a Docker Engine.
1

Add a New Runner

In the left-hand side navigation bar select Runners and proceed by clicking the “New Runner” button in the top-left corner. A dialogue box will then open.
2

Fill in the Parameters

  • Name: Enter a name for the Runner group.
  • Tags: Add or create tags (optional).
  • Default: Check this box to set this Runner group as the default. When enabled, any workflows that do not explicitly specify a Runner group will automatically be assigned to this one.
3
Click on the CloudFormation option and click on the blue Cloudformation stack link.
4

Sign into your AWS Account

Please sign into your AWS Account if you are not already signed in. You will then be redirected to a new page where you must fill out the Quick create stack form.
5

Enter the values in the form as follows

6

Create Stack

Once you have entered all the correct values click ‘Create stack’. AWS will create a stack form with all the specific values you filled out in the form.
7

Navigate to the Runners page in the **Blink Platform**

Click ‘Close’. You can then head over to the Runners page in the Blink Platform, where you will see that your runner is now connected and how many instances it has.
8

Connecting to the Runner Host created with CloudFormation

Once the stack is fully created from the above template, navigate to the Outputs tab. There you can find the Ec2InstanceUser and Ec2InstancePublicDnsName outputs, among others. Using the values of these 2 outputs and the key file which corresponds to the EC2 Key Pair you selected when creating the stack (The file should have been downloaded when the Key Pair was created), you should be able to log in to the Runner host by running the following command (given that the IP of the host from which you’re running the command is within the range defined by the CIDR block you specified when creating the stack):

Deploying a Runner

Learn how to deploy a Blink Runner to execute workflows securely within your environment.

Deploying a Runner with Docker

Guide to installing, configuring and deploying a Runner using Docker

Deploying a Runner with Kubernetes

Guide to installing, configuring and deploying a Runner using Kubernetes

Configuring a Runner Group

Deploy multiple on-prem Runners for high availability, parallel execution, or workload isolation.