Structure recommendation

You can't build a great building on a weak foundation

First and foremost you need to have strong Google Cloud foundations. And this starts by leveraging at best Google Cloud folders and projects; once you have those foundation layers designed and implemented efficiently, you will gain visibility and set the stage for efficient security and networking implementation. Those foundations are fundamental and if not done properly will slow down at every step when your footprint on Google Cloud grow.

Organization policies (discussed in ext section) that are considered as your "security constitution" on Google Cloud can only be done and propagate properly if there is no clear structure of folders and projects for your Google Cloud organization.

By getting the role "browser" on your organization, we will be able to get an overview of your current "AS IS" structure and already make some recommendations. We will then discuss with your Google Cloud infra team to understand the approach taken and how we envision a "TO BE" based on your company structure.

We will offer recommendations on the following aspects:

Resources Hierarchy

Detailed architecture with folders and projects with those bests practices in mind:

• Use a simple folder structure

• Use folders and projects to reflect data governance policies

Resource labels and tags

Use labels and tags when you start to use Google Cloud products, even if you don't need them immediately. Adding labels and tags later on can require manual effort that can be error prone and difficult to complete.

A tag provides a way to conditionally allow or deny policies based on whether a resource has a specific tag. A label is a key-value pair that helps you organize your Google Cloud instances.

You can use labels for multiple purposes, including the following:

• Managing resource billing: Labels are available in the billing system, which lets you separate cost by labels. For example, you can label different cost centers or budgets.

• Grouping resources by similar characteristics or by relation: You can use labels to separate different application lifecycle stages or environments. For example, you can label production, development, and testing environments.

• Support cost and billing reporting