When connected to Bastion host, why id changed to Service Acct?
Hi Matt - Under the Bastion Host lecture, when logged from external host to Bastion host, why the account changed from login account (used while doing "gcould init") to service account? If I compare with on-prem hosts using my ID, if I SSH from one host to another, it displays user id as my own on the 2nd host .
Why is the behavior on GCP is different?
Further, in order to connect from Bastion host to another Internal host, you mentioned that the Compute Engine scope for the service account needs to be enabled. Is it about attaching a policy/role (something like compute.editor) to the service account? Can you please elaborate on this?