video1.0<iframe src="https://www.loom.com/embed/150b4ee6c4e34066b282a47dbc943518" frameborder="0" width="1280" height="960" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>9601280Loomhttps://www.loom.com9601280https://cdn.loom.com/sessions/thumbnails/150b4ee6c4e34066b282a47dbc943518-da14a909150a4f24.gif642.942This Loom explains how to fix missing internet access for an AWS private subnet by updating its route table to use a NAT gateway. The author first describes the private subnet’s route table and finds there is no explicit rule sending non-VPC traffic to the NAT gateway, even though the private subnet has no direct internet access by default. They confirm the NAT gateway is healthy with status succeeded. After creating a route that sets destination to public access (0.0.0.0/0) and targets the NAT gateway with a return enabled flag, they validate the fix using validate.sh and a TCP TLS curl test that successfully resolves the API host and reaches a public GitHub link.