This is the workaround provided by Bitnami support. I have not verified as yet but wanted to get the info out.
We have been able to reproduce this issue. It is effectively a bug in the Google Cloud Launcher tool, since it only shows networks that belong to a specific VPC Service Project, and not networks that have been shared to that VPC Service Project from the VPC Host Project.
We would encourage you to contact with Google to check this issue, as it is for sure affecting other users with similar configurations.
However, in the meantime, you can workaround this issue by doing the following:
-Inside a VPC Service Project, which will be the final destination of your instance, launch the instance via the Google Cloud Launcher to a non-shared VPC. Ensure it is deployed to your desired cloud region (e.g. "us-east-1").
-Once deployed, create a snapshot of the instance, and delete the instance afterwards.
-Now, in the same VPC Service Project and inside the Google Cloud console, go to Compute Engine -> VM instances, click on "Create Instance" and enter the following information:
Region: The same one to which the snapshot was saved.
Boot disk: Select the snapshot which contains the ELK installation, created previously.
Click on "Management, security, disks, networking, sole tenancy" -> Networking -> Edit the default network instance -> Change from "Networks in this project" to "Networks shared with me (from host project [...])", and then finally select your destination shared network.
Set the appropriate network tags.
IMPORTANT: Note that you may manually need to create the network tags or firewall rules in the shared VPC Host project (not the VPC Service Project).
Once launched, you should have your desired application (ELK) working properly in the shared VPC network you chose.