As a project for learning, it seems very interesting. For production workloads, this doesn't seem like an efficient architecture.
Personally, I tend to stay away from EC2 as much as I can. You can probably run 80-90% of workloads on AWS Lambda nowadays. Looking superficially at your idea, I don't see a reason why you couldn't go Serverless. I would also use AWS API Gateway to interface HTTP requests with Lambda. That would be my primary choice.
I don't know if it would be possible, but maybe you can use API Gateway as a proxy to the Github API directly. You can transform incoming requests to match Github specs, and also customize responses to the clients commenting.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As a project for learning, it seems very interesting. For production workloads, this doesn't seem like an efficient architecture.
Personally, I tend to stay away from EC2 as much as I can. You can probably run 80-90% of workloads on AWS Lambda nowadays. Looking superficially at your idea, I don't see a reason why you couldn't go Serverless. I would also use AWS API Gateway to interface HTTP requests with Lambda. That would be my primary choice.
I don't know if it would be possible, but maybe you can use API Gateway as a proxy to the Github API directly. You can transform incoming requests to match Github specs, and also customize responses to the clients commenting.