Error: A timeout of 5 minutes is exceeded. Please ensure your EC2 instance has access to the Internet.

[machulav]

Error: A timeout of 5 minutes is exceeded. Please ensure your EC2 instance has access to the Internet.

[davinchia]

If you run it in the private subnet, please make sure you use NAT Gateway with this subnet, so your instance with private IP has access to the Internet and can pull the jobs from GitHub. Otherwise, the instance with the private IP won't be able to connect to the internet.

@machulav you were right - worked once I attached a NAT gateway!

[machulav]

Hey @davinchia,

The instance is currently running in a private VPC/subnet with a private IP. Does the instance need a public IP?

If you run it in the private subnet, please make sure you use NAT Gateway with this subnet, so your instance with private IP has access to the Internet and can pull the jobs from GitHub. Otherwise, the instance with the private IP won't be able to connect to the internet.

I hope it helps!

[machulav]

Hey @mikemhenry, thanks for your question!

The issue could be related to the type of EC2 instance you selected: t4g.micro is based on ARM64 CPU architecture, and the action currently uses x64 compatible GitHub Action Runner package as you can see here: https://github.com/machulav/ec2-github-runner/blob/main/src/aws.js#L13

As a result, I would expect that the runner is just can not be started on your EC2 instance and register itself in your GitHub repository. Try to use x64 compatible EC2 instance.

I hope it helps!

[mikemhenry]

I'm sure that is the issue! I am looking at this again today. Do you intend on supporting multiple architectures? Perhaps it defaults to x86 but could support arm64? It is a pre-release but I am interested in helping you test if needed.

[davinchia]

Hi, I'm running into this even on an intel based instance. This is my yaml.

My security group is also wide open for testing, both inbound and outbound. Any tips on how one would go about debugging this?

The instance is currently running in a private VPC/subnet with a private ip. I'm running this from a public OSS repo, does the instance need a public ip?

[machulav]

I'm sure that is the issue! I am looking at this again today.

@mikemhenry, I hope you resolve the issue!

Do you intend on supporting multiple architectures? Perhaps it defaults to x86 but could support arm64?

Yeah, it's definitely a good point to support multiple architectures! Created a new issue for that #37

It is a pre-release, but I am interested in helping you test if needed.

Cool, thanks a lot! I will notify you when it's ready for testing.