Create AMI of EC2 instance with GitHub Actions runner installed
Hi AWS, I am trying to create AMI for the EC2 server (Windows/Linux) where the GitHub Actions self-hosted runner is installed and now I need to know if I will create the snapshot and then AMI and then spin up a new server what impact will it have on that new server in terms of security and port. As you know when you configured the GitHub Actions self-hosted runner there is a token that is used for authentication so will that token exist on the newly created server from AMI of that instance or not. Also what can be the potential security risks which needs to be highlighted from audit aspect.
Having said that I am not sure if GitHub has official documentation for such a scenario as they provide more sort of a self-service environment for installing it.
Please guide.
- Newest
- Most votes
- Most comments
I looked at this year ago with bitbucket and each ec2 had its own api key.
This article may be what you’re looking for for GitHub because each ec2 will be identical you need to treat it as an asg https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners
Relevant content
- asked 4 months ago
- asked 8 months ago
AWS OFFICIALUpdated 8 months ago- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 8 months ago
Hey @Gart Mclean, can you please elaborate it a bit more. Sorry but I am not able to recall what you mentioned in the comment. I am thinking what if I am going to snapshot the EC2 instance where the GitHub self-hosted runner is installed, and there is a token associated with each runner, will the snapshot use the same token or it will be different?