New EC2 servers unavailable via Public IP's

Asked Apr 06 '16 at 14:09

Active Apr 06 '16 at 14:09

Viewed 26 times

I've created a new VPC with the 172.21.0.0/16 subnet. I proceeded to launch an instance into it with a public IP.

Unfortunately the instance does not come online. Instances that I launch in another VPC/subnet do work fine.

I thought instances with a public IP would always have working internet functionality in AWS.

Do I have to reconfigure the VPC?

asked Apr 06 '16 at 14:09

ujjain

1

AWS has private and public subnets. Does your subnet have an IGW (internet gateway)? – ceejayoz Apr 06 '16 at 14:14

0 Answers0