Protect Your Network with Cloud NAT

Moving your internal services to the cloud can bring you a handful of new, useful features, but one of the biggest challenges is protecting your internal endpoints.
Removing public IP addresses to protect your environment has been a long kept best practice. The real conundrum comes when trying to configure those instances with public Internet access when you need it. Stephanie covers how to do just that using Cloud NAT.
Cloud Network Address Translation → goo.gle/2lW5O26
Watch other episodes of this series here → goo.gle/2ZmtZEY
Get notified when new episodes are released by subscribing to the GCP Channel → goo.gle/GCP
product:Cloud NAT; fullname: Stephanie Wong;
#NetworkingEndToEnd

[@SheldonWarkentin]

Great overview! If a video does not exist yet, it would be great to see how Cloud NAT can be used with a GKE Private Cluster to support egress to whitelisted endpoints from private Nodes. Thank you!

[@UTECHPIA]

Really great delivery! Thanks for the excellent content, Stephanie! 👍

[@CVS-nh4gw]

Good video. Slowing down the presentation will be my suggestion.

[@faisalee]

Awesome! Great delivery makes understanding easier :)

[@furry2fun]

how did you ssh from bastion host to web server? can you explain the commands?

[@zeyadsabti5484]

Thanks a lot. Greetings from Iraq.

[@joeb.1163]

Really helpful.. Thank you

[@ayushthakur736]

NAT is the key

[@ashleyboykin7777]

are the NAT IP addresses atuo created by Google?

[@mnasruul]

NAT IP addresses will created auto if your chose "Automatic", if you choose Manual you will setup name manually by the IP address will given auto

[@mnasruul]

Thanks sw

[@kacper9207]

✔🌟✔