Open jpluscplusm opened 2 years ago
Hey all 👋
https://github.com/awsdocs/elb-network-load-balancers-user-guide/commit/21dc1ffe9c9dab6e24f181b8b310dfc88382f134#diff-b3c41e866253fd714e911e5df66b9c58de3eb6c08200f09d8ccb8c2d050f47aaL18 changed the restriction from named instance types to "Nitro instances" ..
... and then https://github.com/awsdocs/elb-network-load-balancers-user-guide/commit/7afdbe65174dd66168aec8fe4934c73659bf3ab8#diff-3eab451a4033fc86129770b0699db9da9c4f69c700c8b3995a3a0355aff884afL7 changed the restriction to "VPC peers require ip-address targets, not instance-ids".
Hey all 👋
611 reflected the AWS docs at that point in time but, reviewing them today I can't see any indication on the linked AWS troubleshooting page that cross-VPC NLB connectivity/reachability is still a function of consumer instance type.
https://github.com/awsdocs/elb-network-load-balancers-user-guide/commit/21dc1ffe9c9dab6e24f181b8b310dfc88382f134#diff-b3c41e866253fd714e911e5df66b9c58de3eb6c08200f09d8ccb8c2d050f47aaL18 changed the restriction from named instance types to "Nitro instances" ..
... and then https://github.com/awsdocs/elb-network-load-balancers-user-guide/commit/7afdbe65174dd66168aec8fe4934c73659bf3ab8#diff-3eab451a4033fc86129770b0699db9da9c4f69c700c8b3995a3a0355aff884afL7 changed the restriction to "VPC peers require ip-address targets, not instance-ids".