2 Answers
Hi Ryan,
Yes, I agree. The quiz question is incorrect….I just pushed an update.
–Scott
Hi Scott regarding this question How would an Internet initiated Connection be able to reach to an instance with just a private ip through a NAT Instance. I thought for an instance with a private ip to receive an inbound request it should be behind an Internet Facing Load Balancer. However this question seems to confuse me further with NAT instance being a way for it to receive inbound. Can you kindly explain on this further
Now you changed it to "You want to deny public internet initiated connections to your private instances."
How is different when you use a NAT GW ?
Not sure if I got your question correctly, but NAT Gateway does not allow internet initiated connections reach your private instances (but onliy private instances initiated connections reach the internet).
I think this is ambiguous. Surely whilst you may configure a NAT instance to forward Internet initiated connection to instances with only private addresses this seems counter-intuitive. Why would you do that unless as a hack? Surely you’d just make the target instance public? The usual intention with NAT instances is for outbound access. Anything else is surely a highly custom networking requirement?