1 個回答
- 最新
- 最多得票
- 最多評論
0
A few months ago, I started working on a very similar solution and came up with the following scalable and cost-efficient solution.
- GitHub sends a webhook event when starting a job.
- The API Gateway receives the event.
- A Lambda function validates the event and sends a message to SQS.
- Another Lambda function reads the message from SQS and launches an EC2 instance in an VPC of your choice.
- The EC2 instance starts and registers the GitHub runner.
- The GitHub runner executes the job.
- The EC2 instance terminates itself.
My solution is called HyperEnv for GitHub Actions Runner.
已回答 4 個月前
相關內容
- 已提問 6 個月前
- 已提問 6 個月前
- AWS 官方已更新 7 個月前
- AWS 官方已更新 4 個月前
- AWS 官方已更新 3 個月前