Can peered VPCs use firewall rules that reference tags and service accounts

Question

I have 2 VPCs peered together, aaa and bbb.

In aaa I have a VM host-aaa with a network tag tag-aaa, and in bbb I have a VM host-bbb with a network tag tag-bbb.

Can I create a firewall rule in aaa that allows ingress into host-aaa from host-bbb based on network tags?

Answer 1

In the Google Cloud Console, go to the VPC Network Peering tab.
The status of VPC Network Peering is "Connected."
Check the other project's VPC Network Peering page to see whether it also reads "Connected."

Consider the case when two separate external firms, SaaS1 and SaaS2, are required to provide services to VM instances in network-a. Two peering connections are necessary to access both using only internal IP addresses:

In SaaS1, network-a interacts with network-b; in SaaS2, network-a interacts with network-c.
Network-b and network-c can be in distinct projects and organisations with VPC Network Peering.