3 ms·
"Security groups (which define what IPs can access what ports, similar to basic IPTables firewall rules) cannot be shared between EC2-Classic and EC2-VPC," Tha
by sciurus 12y ago
"Security groups (which define what IPs can access what ports, similar to basic IPTables firewall rules) cannot be shared between EC2-Classic and EC2-VPC,"
That is no longer true. In December 2014 Amazon launched ClassicLink, which lets you add EC2-Classic instances to VPC security groups.
https://aws.amazon.com/blogs/aws/classiclink-private-communication-between-classic-ec2-instances-vpc-resources/ https://aws.amazon.com/blogs/aws/classiclink-private-communi...
http://www.youtube.com/watch?v=HexrVfuIY1k&t=33m33s http://www.youtube.com/watch?v=HexrVfuIY1k&t=33m33s
- tirus 12y agoAuthor here - Actually, the big problem was RDS EC2-Classic DB security groups, which ClassicLink doesn't help with. ClassicLink certainly is a feature, but it's not one that would have helped with the subset of groups that we were having trouble with.
- deleted 12y ago[deleted]
- tirus 12y agoWhat a coincidence - that's exactly what I did too, except I used IPTables and just PATed the connections.