Why we have to create a new project for a big query? Can’t we managed within the existing project?
Hey, there… I’m glad you’re asking.
Do you need to make a new project, for it to work? No.
Does doing what I have you do teach you things that are important to a Cloud Engineer? Yes, definitely.
You need to be comfortable going beyond the auto-created stuff and managing the details of setting up projects, managing their billing, and controlling access to all the pieces. This lab steps you through some of that stuff.
Does that help give some context? 🙂
Hey Mattias, I think the "Billing / Project" related videos need to be reworked to be a little more elaborate, especially explaining "why" we are doing a certain thing and why "not" another thing, probably taking a use case scenario of a company as an example. As for myself, despite knowing AWS (being AWS Dev and SAA certified), I found it difficult to relate to what has been explained about creating a new "Admin" project (or you could say I was not able to build a mental model around the "Billing / Project" concept). Probably some visualization of the hierarchy or flow, along with some explanation would be helpful. Some questions that I could think of, to give you an idea of the gap that needs to be filled to make it perfect:
Export must be set up per billing account -> But in what scenario would we have multiple billing accounts?
Is it related to multiple teams having their respective "projects" and each project having it’s own billing account?
Or could those teams / projects share the same billing account?
Is the "Admin" project created for use by the "Admin" team of the company? Or the sole purpose of that project is to export to BigQuery?
Are both, the "Admin" as well as the newly created "Billing Account user", able to manage the same billing account but not able to access each other’s projects?