Aws git access/curl issue

Asked Feb 23 '18 at 11:30

Active Feb 23 '18 at 11:30

Viewed 112 times

I am having something strange using AWS subnet with ubuntu instances.

I have create the public/private subnet schema with one ubuntu instance on the private one. Everything is working smoothly, I can git clone, curl...

However when creating any other ubuntu instance on the private subnet within the same VPC, I can't use git at all, even a simple curl to https://gitlab.com is not working (getting no answer).

I tried an other url like google and got a successful result.

Do you have an idea why I am getting this behaviour and specially only for gitlab?

Appreciate your help

asked Feb 23 '18 at 11:30

Pierre Sigwalt

Are they in the same security group? – swigganicks Mar 07 '18 at 19:52
Hi, Yes they are in the same security group. What's changing is the subnet but within the same VPC. – Pierre Sigwalt Mar 12 '18 at 01:01
If you've already checked the route tables and ensured that there is http access on the neccessary ports, set up a VPC flow log and check the rejected traffic logs. It will let you know why it's not working – swigganicks Mar 12 '18 at 01:18

Aws git access/curl issue

0 Answers0