Resource Hierarchy:

• The Resource Hierarchy is almost similar to the Linux file system.
• Each child object has only one parent
• You may find it easiest to understand the GCP resource hierarchy from the bottom up.
• All the resources you use–whether they are virtual machines, Cloud Storage buckets, tables in BigQuery, or anything else in Google Cloud are organized into projects.
• Optionally, these projects may be organized into folders; folders can contain other folders.
• All the folders and projects used by your organization can be brought together under an organization node.
• Projects, folders, and organization nodes are all places where policies can be defined. Some GCP resources let you put policies on individual resources, too, like Cloud Storage buckets.
• Permissions are inherited from top to down

Organization Resource:

• Represents an organization (e.g., a company) and is the root node in the GCP resource hierarchy.
• IAM access control policies applied to the Organization resource are applied throughout the entire below hierarchy (through Folders, Projects, and Resources)
• Can grant access to different people in the organization
• Not applicable to personal (e.g., Gmail) accounts.
• For Free Gmail accounts, you can see from Project Level only.

Folders:

• Additional (optional) grouping and isolation boundaries between projects
• Collection of projects and other folders
• IAM roles applied to the folder apply to all projects inside

Projects:

• Each GCP project has a name and project ID you assign
• The project ID is a permanent, unchangeable identifier, and it has to be unique across GCP.
• You will use project IDs in several contexts to tell GCP which Project you want to work with.
• On the other hand, project names are for your convenience, and you can change them
• Required to use any GCP resources
• The basis for creating, enabling, using, and paying for GCP service
• Identifiers
  • Project ID (must be globally unique)
  • Project number (automatically generated)
  • Project name (“Friendly name”)
  • Good practice to have identical Project name and ID
• The Cloud Resource Manager provides methods that you can use to programmatically manage your projects in Google Cloud Platform.
• With this API, you can do the following:
  • Get a list of all projects associated with an account.
  • Create new projects.
  • Update existing projects.
  • Delete projects.
  • Undelete, or recover, projects that you don’t want to delete

Resources:

• Everything that is created and used on GCP

Google Cloud Resource Hierarchy

– Organization (root node)

– Folders (optional)

– Projects

– Resources (inside projects)

Note:- Project ID we can edit first time only once.