Ec2 instance on AWS apt- get not working

Question

I have Ec2 instance on AWS with Amazon Ubuntu.

When i try to download any thing, I am unable to do so.

For Ex:

~# apt-get update

0% [Connecting to ap-southeast-1.ec2.archive.ubuntu.com (103.246.148.161)] [Connecting to security.ubuntu.com (91.189.91.15)

Another Ex will be

~# wget https://s3.amazonaws.com/aws-cli/awscli-bundle.zip

--2014-04-09 07:27:17--  https://s3.amazonaws.com/aws-cli/awscli-bundle.zip
Resolving s3.amazonaws.com... 207.171.189.80
Connecting to s3.amazonaws.com|207.171.189.80|:443...

This remains forever.

I was able to download files until I created Group and user for AWS Console.

Please suggest what can be issues here.

score 57 · Answer 1 · answered Apr 10 '14 at 05:49

57

You EC2 instances's Security groups is not configured to let it reach internet. You need to have an Outbound rule for all traffic to 0.0.0.0/0. In EC2-Classic, this is already in place and hence you need not worry. However, if this is in VPC, then you need to add this rule.

Also, Apart from what is said above, could you check whether any iptables rules causing any issue.

answered Apr 10 '14 at 05:49

slayedbylucifer

22,878
16
94
123

2

Also make sure you have assigned a public ip to the instance, I just wasted some time until I realized what the issue was. – NikoNyrh Aug 29 '16 at 07:56
2

@NikoNyrh, You do not need a public IP for this purpose. If that is how you got it working, then your doing something completely wrong. – slayedbylucifer Aug 29 '16 at 13:45
Without a publicly accessible ip my EC2 instance couldn't even ping google.com or 8.8.8.8, maybe this only happens when being part of a company's VPC. I could SSH in by using the "internal" ip via VPN but couldn't connect out to open internet. – NikoNyrh Aug 29 '16 at 17:57
If you forgot you can go into the existing subnet and choose "automatically assign public IP" – nettie Sep 20 '18 at 15:16

score 5 · Answer 2 · answered Feb 05 '18 at 13:34

5

Also make sure that if you want to download anything using wget using HTTPS link .Then add Outbound Rule for HTTPS ( Port 443 ) to 0.0.0.0/0

answered Feb 05 '18 at 13:34

Omkar Jadhav

1,046
3
16
41

score 1 · Answer 3 · answered Jul 17 '17 at 08:22

1

adding outbound rule HTTP TCP 80 0.0.0.0/0 work for me.

answered Jul 17 '17 at 08:22

Xavier

11
1

score 1 · Answer 4 · answered May 16 '19 at 07:59

1

I faced same issue because I did not enable nat gateway for private subnet in vpc.

If your machine is in private subnet you'll have to enable nat gateway in route table for that subnet.

It ll look like this after enabled

answered May 16 '19 at 07:59

Shree Prakash

2,052
2
22
33

score 0 · Answer 5 · answered Oct 31 '18 at 06:51

I figured out how to get apt-get to work again.

Edit gai.conf:

sudo vim /etc/gai.conf

change line ~54 to uncomment the following:

precedence ::ffff:0:0/96 100

write and quit:

:wq

CAUTION

Look out line 50 which looks almost identical:

precedence ::ffff:0:0/96 10

This is the wrong line. Go ~4 lines down and you'll find the correct line to uncomment because it ends with 100 instead of 10

score 0 · Answer 6 · answered Feb 01 '22 at 14:10

If the problem is not in your Security group, you might have forgotten to add the Ephemeral ports in the VPC/Subnet Network ACL.

In your route table, Allow inbound rule TCP traffic from 32768 - 65535 on 0.0.0.0/0

If you have only enabled 80, 443 in outbound, then the return traffic still comes through the temporary ports listed above. Only enabling 80, 443 outbound will not let your server complete a curl google.com

The ephemeral port list mentioned above is for ubuntu, You can check yours by running sysctl net.ipv4.ip_local_port_range

Ec2 instance on AWS apt- get not working

6 Answers6

Linked