gcp creating cloud nat gateway for a cusom vpc and getting a public ip

While creating either vpc or cloud nat gateway is not really a thing, but it can be confusing when you trying to wonder where is the public ip associated with it? 

It is allocated automatically. all you need to do is 

- create custom vpc say mytest-vpc

- create cloud nat gateway 

- then place vm instance in the subnet and you can see your public ip address appearing 

This is my custom vpc network.



And then placing the VM in the subnet 





When you ssh into that box, you will notice there's a public ip address appearing. 


 



Comments

Post a Comment

Popular posts from this blog

The specified initialization vector (IV) does not match the block size for this algorithm

Image
If you're getting  exception when trying to assigned key to a symmetric key and getting error message below :- The specified initialization vector (IV) does not match the block size for this algorithm And your code probably look like something below :- Then you need to go into debug mode and start looking into the supported size for IV as shown in diagram below :- As you can see, IV is 16 bytes, so you need to provide 16 bytes. The same goes for Key field too, if you're adding anything to it. As long as you provide a valid key size, then we're good and you're code will be ready.
Read more

NodeJS: Error: spawn EINVAL in window for node version 20.20 and 18.20

Encounter this issue when running autorest (that uses nodejs).  I am using node version:  v18.20.2 After i revert to use node v18.12.0, then i was able to get my app to run without this error. Since i am working with Azure devops yaml, i was able to use the following to resolve my issue.  - task : NodeTool@0   inputs :     versionSource : 'spec'     versionSpec : '18.18.0'
Read more