One possible next improvement is to use this AMI and the User Data script in an infrastructure-as-code DSL like Terraform or Cloudformation. Now that we have a reusable image (AMI) for a self-hosted Gitlab runner, it can be used as a building block for further automation. This tag matches the environment passed to the gitlab-runner-register.sh script above. gitlab-ci.yml each job will have to use a tag to run that job on the new Gitlab runner. When defining the Gitlab CI / CD pipeline in. Click on Enable for this project to make the runner usable by the repository.Īt this point, the Gitlab runner is attached to the project. going back to the repository's settings -> CI / CD -> Runners -> Specific Runners, this new runner should be available in the list.Call the following script from the User data section of EC2's instance launch options to register the runner with : launch a new EC2 instance using the AMI ID found in the previous step.login the AWS Console and check the EC2 -> AMIs section to confirm that the new Gitlab runner AMI is there.Packer build -var 'aws_access_key=' -var 'aws_secret_key=' gitlab-runner.json build the Gitlab runner image using Packer:.install Hashicorp's Packer on your build machine.This can be found in the above mentioned repository settings -> CI / CD -> Runners -> Specific Runners -> Set up a specific runner manually a repository that needs a CI / CD set up.If that environment is AWS and you are looking for an automated way of setting up the Runner(s) on EC2, then stay tuned for a 56k.cloud recipe! This comes in handy when the CI jobs have to run in a user-owned environment or more powerful runners are needed. allows its users to run their own, self-hosted, Gitlab Runners as part of their Gitlab CI feature.

How to install gitlab on aws ec2