Skip to content

Latest commit

 

History

History
101 lines (73 loc) · 8.35 KB

GoogleCloudPlatformResources.md

File metadata and controls

101 lines (73 loc) · 8.35 KB

Google Cloud Platform resources

  1. IAM - https://cloud.google.com/iam/docs/overview
    IAM in GCP allows you to manage access control by defining who (identity) has what access (role) for which resource. In IAM, permission to access a resource isn't granted directly to the end user. Instead, permissions are grouped into roles, and roles are granted to authenticated principals.

⭐ A principal can be a Google Account (for end users), a service account (for applications and compute workloads), a Google group, or a Google Workspace account or Cloud Identity domain that can access a resource. Each principal has its own identifier, which is typically an email address.
⭐ A role is a collection of permissions. Permissions determine what operations are allowed on a resource. When you grant a role to a principal, you grant all the permissions that the role contains.
⭐ The allow policy is a collection of role bindings that bind one or more principals to individual roles. When you want to define who (principal) has what type of access (role) on a resource, you create an allow policy and attach it to the resource. \

Additional Resources Link
Understanding Google Cloud IAM Roles https://cloud.google.com/iam/docs/understanding-roles
IAM conditions https://cloud.google.com/iam/docs/conditions-overview
Creating and managing Tags https://cloud.google.com/resource-manager/docs/tags/tags-creating-and-managing
Tags and access control https://cloud.google.com/iam/docs/tags-access-control
  1. Billing - https://cloud.google.com/billing/docs To use Google Cloud services, you must have a valid Cloud Billing account, and must link it to your Google Cloud projects. Your project's Google Cloud usage is charged to the linked Cloud Billing account. When you # for NIH CloudLab (https://cloud.nih.gov/resources/cloudlab/) you will access an account loaded with credits for you to experiment with.
Additional Resources Link
Price list for all resources https://cloud.google.com/#/list
GCP # Calculator https://cloud.google.com/products/calculator
Billing best practices https://cloud.google.com/docs/enterprise/best-practices-for-enterprise-organizations#billing_and_management
Setting budgets and alerts https://cloud.google.com/billing/docs/how-to/budgets
Use cloud resource labels to track costs by function https://cloud.google.com/blog/topics/cost-management/use-labels-to-gain-visibility-into-gcp-resource-usage-and-spending
Export billing to big query for analysis https://cloud.google.com/billing/docs/how-to/export-data-bigquery
  1. Cloud Storage - https://cloud.google.com/storage/docs/introduction
Additional Resources Link
Understanding Google Cloud IAM Roles https://cloud.google.com/iam/docs/understanding-roles
IAM conditions https://cloud.google.com/iam/docs/conditions-overview
Creating and managing Tags https://cloud.google.com/resource-manager/docs/tags/tags-creating-and-managing
Tags and access control https://cloud.google.com/iam/docs/tags-access-control
  1. VertexAI - https://cloud.google.com/vertex-ai/docs/start/introduction-unified-platform

⭐ A principal can be a Google Account (for end users), a service account (for applications and compute workloads), a Google group, or a Google Workspace account or Cloud Identity domain that can access a resource. Each principal has its own identifier, which is typically an email address.
⭐ A role is a collection of permissions. Permissions determine what operations are allowed on a resource. When you grant a role to a principal, you grant all the permissions that the role contains.
⭐ The allow policy is a collection of role bindings that bind one or more principals to individual roles. When you want to define who (principal) has what type of access (role) on a resource, you create an allow policy and attach it to the resource. \

Additional Resources Link
Understanding Google Cloud IAM Roles https://cloud.google.com/iam/docs/understanding-roles
IAM conditions https://cloud.google.com/iam/docs/conditions-overview
Creating and managing Tags https://cloud.google.com/resource-manager/docs/tags/tags-creating-and-managing
Tags and access control https://cloud.google.com/iam/docs/tags-access-control
  1. Cloud Build - https://cloud.google.com/billing/docs

⭐ A principal can be a Google Account (for end users), a service account (for applications and compute workloads), a Google group, or a Google Workspace account or Cloud Identity domain that can access a resource. Each principal has its own identifier, which is typically an email address.
⭐ A role is a collection of permissions. Permissions determine what operations are allowed on a resource. When you grant a role to a principal, you grant all the permissions that the role contains.
⭐ The allow policy is a collection of role bindings that bind one or more principals to individual roles. When you want to define who (principal) has what type of access (role) on a resource, you create an allow policy and attach it to the resource. \

Additional Resources Link
Understanding Google Cloud IAM Roles https://cloud.google.com/iam/docs/understanding-roles
IAM conditions https://cloud.google.com/iam/docs/conditions-overview
Creating and managing Tags https://cloud.google.com/resource-manager/docs/tags/tags-creating-and-managing
Tags and access control https://cloud.google.com/iam/docs/tags-access-control
  1. Google Lifescience API - https://cloud.google.com/billing/docs

⭐ A principal can be a Google Account (for end users), a service account (for applications and compute workloads), a Google group, or a Google Workspace account or Cloud Identity domain that can access a resource. Each principal has its own identifier, which is typically an email address.
⭐ A role is a collection of permissions. Permissions determine what operations are allowed on a resource. When you grant a role to a principal, you grant all the permissions that the role contains.
⭐ The allow policy is a collection of role bindings that bind one or more principals to individual roles. When you want to define who (principal) has what type of access (role) on a resource, you create an allow policy and attach it to the resource. \

Additional Resources Link
Understanding Google Cloud IAM Roles https://cloud.google.com/iam/docs/understanding-roles
IAM conditions https://cloud.google.com/iam/docs/conditions-overview
Creating and managing Tags https://cloud.google.com/resource-manager/docs/tags/tags-creating-and-managing
Tags and access control https://cloud.google.com/iam/docs/tags-access-control
  1. Operations (formerly Stackdriver) https://cloud.google.com/stackdriver/docs

⭐ A principal can be a Google Account (for end users), a service account (for applications and compute workloads), a Google group, or a Google Workspace account or Cloud Identity domain that can access a resource. Each principal has its own identifier, which is typically an email address.
⭐ A role is a collection of permissions. Permissions determine what operations are allowed on a resource. When you grant a role to a principal, you grant all the permissions that the role contains.
⭐ The allow policy is a collection of role bindings that bind one or more principals to individual roles. When you want to define who (principal) has what type of access (role) on a resource, you create an allow policy and attach it to the resource. \

Additional Resources Link
Understanding Google Cloud IAM Roles https://cloud.google.com/iam/docs/understanding-roles
IAM conditions https://cloud.google.com/iam/docs/conditions-overview
Creating and managing Tags https://cloud.google.com/resource-manager/docs/tags/tags-creating-and-managing
Tags and access control https://cloud.google.com/iam/docs/tags-access-control