Pricing - Virtual Networks Module 1.2.4

Question 1

About ingress traffic, what is considered ingress traffic

Answer 1

Traffic coming in to a Google Cloud resource, such as a VM.
If you send traffic between two VMs, then the traffic is counted as egress traffic as it leaves one VM and counted as ingress traffic as it arrives at the other VM.

Question 2

ingress charges

Answer 2

No charge for ingress traffic. However there may be a charge for resource that processes ingress traffic. Services that process ingress traffic are as follows:
load balancers
claud NAT
protocol forwarding

Question 3

How is egress charged

Answer 3

Egress traffic is charged based on whether the traffic uses an internal or external IP address, whether the traffic crosses zone or region boundaries within Google Cloud, whether the traffic leaves or stays inside Google Cloud, and the network tier of traffic that leaves Google’s network. When two resources communicate with each other, there are two traffic paths—one in each direction. Traffic in each direction is designated as egress at the source and ingress at the destination, and each direction is priced accordingly.

Question 4

egress no charge

Answer 4

Egress to the same Google Cloud zone when using the internal IPv4 addresses or any IPv6 addresses
??? egress to google products(youtube, maps, drive…) or google service in the same zone

Question 5

egress charge

Answer 5

everything else, between zones - external, between regions…

Question 6

Why is difference in egress traffic to the same zone (external IP between VMs in the same zone charged)

Answer 6

Compute Engine cannot determine the zone of a virtual machine through the external IP address.
Therefore, this traffic is treated like egress between zones in the same region.