Yum update error on ami-vpc-nat-1.0.0-beta.x86_64-ebs AWS image

I am just starting with a brand new VPC with both a NAT server and a hardware VPN, more about the hardware VPN later, that was fun to configure.

 

When you first start out the VPC does not give you the option of NAT device and hardware VPN, so you have to configure the NAT server separately. The instructions are OK but you have to read them carefully and I did miss which subnet you put the NAT device.

TIP it is the subnet that is classed and public 🙂

 

The instructions for creation of a NAT device in AWS VPC, NOTE that the ami needed for this server has vpc-nat in the name mine is (ami-vpc-nat-1.0.0-beta.x86_64-ebs)

 

Make sure that you follow the instructions for disabling the source/destination checking as well

 

Also you have to associate and Elastic IP Address (EIP) to the EC2 NAT instance. I highlighted EIP as if you talk to the engineers this is what they will call it.

 

Anyway to the problem, to prove it worked you would do a yum update or a yum install lynx. This all appears to work, until you answer yes to the download the packages and then failure. see below:

 

yum update
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 : http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/repodata/repomd.xml
Trying other mirror.
Skipping security plugin, no data
Setting up Update Process
Resolving Dependencies
Skipping security plugin, no data
–> Running transaction check
—> Package aws-amitools-ec2.noarch 0:1.3.57676-1.1.amzn1 set to be updated
—> Package aws-apitools-as.noarch 0:1.0.33.1-1.1.amzn1 set to be updated
—> Package aws-apitools-ec2.noarch 0:1.3.62308-1.1.amzn1 set to be updated
—> Package aws-apitools-mon.noarch 0:1.0.9.5-1.1.amzn1 set to be updated
—> Package aws-apitools-rds.noarch 0:1.3.003-1.1.amzn1 set to be updated
—> Package cloud-init.noarch 0:0.5.14-23.amzn1 set to be updated
–> Finished Dependency Resolution

Dependencies Resolved

=========================================================================================================================================================
Package Arch Version Repository Size
=========================================================================================================================================================
Updating:
aws-amitools-ec2 noarch 1.3.57676-1.1.amzn1 amzn 87 k
aws-apitools-as noarch 1.0.33.1-1.1.amzn1 amzn 5.9 M
aws-apitools-ec2 noarch 1.3.62308-1.1.amzn1 amzn 8.3 M
aws-apitools-mon noarch 1.0.9.5-1.1.amzn1 amzn 5.9 M
aws-apitools-rds noarch 1.3.003-1.1.amzn1 amzn 6.0 M
cloud-init noarch 0.5.14-23.amzn1 amzn 78 k

Transaction Summary
=========================================================================================================================================================
Install 0 Package(s)
Upgrade 6 Package(s)

Total download size: 26 M
Is this ok [y/N]: y
Downloading Packages:
http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/aws-amitools-ec2-1.3.57676-1.1.amzn1.noarch.rpm: [Errno 14] HTTP Error 403 : http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/aws-amitools-ec2-1.3.57676-1.1.amzn1.noarch.rpm
Trying other mirror.
http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/aws-apitools-as-1.0.33.1-1.1.amzn1.noarch.rpm: [Errno 14] HTTP Error 403 : http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/aws-apitools-as-1.0.33.1-1.1.amzn1.noarch.rpm
Trying other mirror.
http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/aws-apitools-ec2-1.3.62308-1.1.amzn1.noarch.rpm: [Errno 14] HTTP Error 403 : http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/aws-apitools-ec2-1.3.62308-1.1.amzn1.noarch.rpm
Trying other mirror.
http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/aws-apitools-mon-1.0.9.5-1.1.amzn1.noarch.rpm: [Errno 14] HTTP Error 403 : http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/aws-apitools-mon-1.0.9.5-1.1.amzn1.noarch.rpm
Trying other mirror.
http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/aws-apitools-rds-1.3.003-1.1.amzn1.noarch.rpm: [Errno 14] HTTP Error 403 : http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/aws-apitools-rds-1.3.003-1.1.amzn1.noarch.rpm
Trying other mirror.
http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/cloud-init-0.5.14-23.amzn1.noarch.rpm: [Errno 14] HTTP Error 403 : http://aaee2bb3-b474-42b9-9ba8-76b552fa9521.s3.amazonaws.com/amzn-v0.9/x86_64/Packages/cloud-init-0.5.14-23.amzn1.noarch.rpm
Trying other mirror.

Error Downloading Packages:
aws-apitools-mon-1.0.9.5-1.1.amzn1.noarch: failure: Packages/aws-apitools-mon-1.0.9.5-1.1.amzn1.noarch.rpm from amzn: [Errno 256] No more mirrors to try.
aws-apitools-as-1.0.33.1-1.1.amzn1.noarch: failure: Packages/aws-apitools-as-1.0.33.1-1.1.amzn1.noarch.rpm from amzn: [Errno 256] No more mirrors to try.
aws-apitools-rds-1.3.003-1.1.amzn1.noarch: failure: Packages/aws-apitools-rds-1.3.003-1.1.amzn1.noarch.rpm from amzn: [Errno 256] No more mirrors to try.
cloud-init-0.5.14-23.amzn1.noarch: failure: Packages/cloud-init-0.5.14-23.amzn1.noarch.rpm from amzn: [Errno 256] No more mirrors to try.
aws-amitools-ec2-1.3.57676-1.1.amzn1.noarch: failure: Packages/aws-amitools-ec2-1.3.57676-1.1.amzn1.noarch.rpm from amzn: [Errno 256] No more mirrors to try.
aws-apitools-ec2-1.3.62308-1.1.amzn1.noarch: failure: Packages/aws-apitools-ec2-1.3.62308-1.1.amzn1.noarch.rpm from amzn: [Errno 256] No more mirrors to try.

 

Weird!!!!, you think that you have got you config wrong.

So try a traceroute

 

traceroute http://www.google.com
traceroute to http://www.google.com (173.194.66.147), 30 hops max, 40 byte packets
1 ec2-79-125-1-102.eu-west-1.compute.amazonaws.com (79.125.1.102) 0.656 ms 0.684 ms 0.880 ms
2 178.236.1.4 (178.236.1.4) 0.889 ms 0.626 ms 0.820 ms
3 178.236.0.138 (178.236.0.138) 1.256 ms 1.473 ms 1.461 ms
4 178.236.0.119 (178.236.0.119) 1.529 ms 1.470 ms 1.453 ms
5 inex.google.com (193.242.111.57) 1.450 ms 1.653 ms 1.665 ms
6 209.85.252.198 (209.85.252.198) 1.577 ms 209.85.252.196 (209.85.252.196) 1.463 ms 1.565 ms
7 209.85.251.191 (209.85.251.191) 13.148 ms 13.265 ms 209.85.250.217 (209.85.250.217) 14.892 ms
8 72.14.232.134 (72.14.232.134) 18.678 ms 18.412 ms 66.249.95.173 (66.249.95.173) 40.221 ms
9 209.85.251.231 (209.85.251.231) 29.199 ms 72.14.236.191 (72.14.236.191) 20.337 ms 216.239.49.45 (216.239.49.45) 18.336 ms
10 we-in-f147.1e100.net (173.194.66.147) 20.314 ms 22.577 ms 20.513 ms

So you have an internet connection and it is working well ??????

 

It turns out that the yum just needs clearing out. How strange but who cares as long as it works

yum clean all
Loaded plugins: fastestmirror, security
Cleaning up Everything
Cleaning up list of fastest mirrors

yum intsall lynx
Loaded plugins: fastestmirror, security
No such command: intsall. Please use /usr/bin/yum –help
[root@ip-172-16-0-10 ec2-user]# yum install lynx
Loaded plugins: fastestmirror, security
Determining fastest mirrors
amzn | 2.1 kB 00:00
amzn/primary_db | 1.5 MB 00:00
Setting up Install Process

 

We

, , ,

  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

ifssoftware.wordpress.com/

Helping you achieve more

The Survival Guides's Blog

How to Survive IT and Holidays

WordPress.com

WordPress.com is the best place for your personal blog or business site.

%d bloggers like this: