GCP — Google Cloud Platform | Functional Structure

Hello Folks , welcome back!! :)

Functional Structure of Google Cloud:

1.1

• Google Cloud’s resource hierarchy contains four levels, and starting from the bottom up they are:
  Resources, Projects, Folders, and an Organization node.

• Resources:
  These represent virtual machines, Cloud Storage buckets or anything else in Google Cloud.Resources are organized into projects, which sit on the second level as per above picture.
• Projects :
  Projects can be organized into folders, or even subfolders, These sit at the third level as per above picture.
• Folders:
  Folders can be organized into organization node as per above picture where you can divide into environments like prod, Stage & Dev.
• Organization:
  Organization which encompasses all the projects, folders, and resources in your organization, this will sit at the top level as per above picture.

1.2

It’s important to understand resource hierarchy because it directly relates to how policies are managed and applied when you use Google Cloud.

Policies can be defined at the project, folder, and organization node levels.

Some Google Cloud services allow policies to be applied to individual resources, too.

1.3

Policies are also inherited downward, This means that if you apply a policy to a folder, it will also apply to all of the projects within that folder.

1.4

• Projects are the basis for enabling and using Google Cloud services, like managing APIs, enabling billing, adding and removing collaborators, and enabling other Google services.

• Each project is a separate entity under the organization node.

• Each resource belongs to exactly one project.

• Projects can have different owners and users.

• Each project owner and users can manage and billing separately.

• Each Google Cloud project has three identifying attributes: a project ID, a project name, and a project number.

• The project ID is a globally unique identifier assigned by Google that can’t be changed after creation, Project IDs are used in different contexts to inform Google Cloud of the exact project to work with.They’re what we refer to as being immutable.

• Project names, however, are user-created. They don’t have to be unique and they can be changed at any time, so they are not immutable.

• Google Cloud also assigns each project a unique project number. It’s helpful to know that these Google-generated numbers exist.

That’s It folks!!
Please provide your feedback in comments and if this article is helpful give a like (clap) :)