Good question! First, HyperEnv deploys an API Gateway + Lambda as well as configures the GitHub webhook automatically. Second, HyperEnv uses a SQS queue to add resiliency, for example to avoid issues caused by rate limiting of the EC2 API. Third, HyperEnv provides an AMI pre-configured to launch a just-in-time GitHub runner. And last but not least, we are maintaining the whole step which includes patching the AMI.
What advantage hyperenv provide over using webhooks to send notification to AWS lambda?
Good question! First, HyperEnv deploys an API Gateway + Lambda as well as configures the GitHub webhook automatically. Second, HyperEnv uses a SQS queue to add resiliency, for example to avoid issues caused by rate limiting of the EC2 API. Third, HyperEnv provides an AMI pre-configured to launch a just-in-time GitHub runner. And last but not least, we are maintaining the whole step which includes patching the AMI.