IAM Roles

Related topics

• IAM permissions is part of IAM Roles From the official documentation: “IAM roles that apply to Cloud SQL and the permissions contained in each role.”
• IAM Roles is part of Identity and Access Management From the official documentation: “IAM roles give the principals permissions to perform tasks on your App Topology resources.”
• custom roles is part of IAM Roles From the official documentation: “This requirement applies to both [predefined roles](/iam/docs/roles-permissions) and [custom roles](/iam/docs/roles-overview#custom).”
• IAM Roles configures service account From the official documentation: “2. [Grant the necessary Identity and Access Management roles](#grant-iam-roles) to your service account.”
• predefined roles is part of IAM Roles From the official documentation: “This requirement applies to both [predefined roles](/iam/docs/roles-permissions) and [custom roles](/iam/docs/roles-overview#custom).”
• IAM permissions works with IAM Roles From the official documentation: “This page lists the IAM roles and permissions for Apigee Registry.”
• IAM policy configures IAM Roles From the official documentation: “When you add a new member to your project, you can use an [Identity and Access Management (IAM)](/iam) policy to give that member one or more IAM roles to control the actions that the member can perform in Migration Center.”
• IAM Roles secures Bigtable From the official documentation: “Access to your Bigtable tables is controlled by your Google Cloud project and the [Identity and Access Management (IAM) roles](/bigtable/docs/access-control#roles) that you assign to users.”
• IAM Roles secures Cloud Storage From the official documentation: “**Fine-grained access control**: Control agent access to Cloud Storage precisely using [IAM roles](/storage/docs/access-control/iam-roles).”
• IAM Roles configures Cloud Storage bucket From the official documentation: “Provide your instance with the `storage.objectAdmin` and `objectViewer` [IAM roles](/storage/docs/access-control/iam-roles) for your bucket.”
• IAM Roles is part of Identity and Access Management (IAM) From the official documentation: “To prevent test disruptions, ensure that your Identity and Access Management (IAM) roles, policies, and failover configurations are correctly set up.”
• IAM Roles secures Knowledge Catalog From the official documentation: “To get the permissions that you need to use the Knowledge Catalog and Looker (Google Cloud core) integration, ask your administrator to grant you the following IAM roles on project where your Looker (Google Cloud core) instance resides:”
• IAM Roles configures linked dataset From the official documentation: “You can't set [IAM roles](/bigquery/docs/access-control) or [IAM policies](/config-connector/docs/reference/resource-docs/iam/iampolicy) on individual tables within a linked dataset. Apply them at the linked dataset level instead.”
• IAM Roles works with service account From the official documentation: “In this section, you designate the service account for the gateway proxies and assign them the correct IAM roles.”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
• custom roles is an alternative to predefined roles From the official documentation: “Generally, we recommend that you [use predefined roles](/iam/docs/choose-predefined-roles) instead of basic or custom roles.”
• Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
• BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
• Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
• BigQuery works with Bigtable From the official documentation: “BigQuery lets you query your Bigtable data from BigQuery.”
• BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
• Cloud Storage works with Google Cloud CLI From the official documentation: “The gcloud CLI is the preferred command line tool for accessing Cloud Storage.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Storage works with Managed Service for Apache Spark From the official documentation: “Managed Service for Apache Spark accesses these files on Cloud Storage.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Bigtable works with Dataflow From the official documentation: “The Dataflow job then writes the transformed data to your Bigtable table.”
• Cloud SQL works with Knowledge Catalog From the official documentation: “You can use Knowledge Catalog to organize and enrich the metadata of Cloud SQL resources.”
• Cloud Storage bucket is part of Cloud Storage From the official documentation: “Create a Google Cloud Storage bucket”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Managed Service for Apache Spark depends on Cloud Storage From the official documentation: “Managed Service for Apache Spark uses Cloud Storage as its default distributed file system.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• BigQuery works with Managed Service for Apache Spark From the official documentation: “This means you can quickly read and write BigQuery data to and from Managed Service for Apache Spark.”
• Bigtable is an alternative to Cloud Storage From the official documentation: “If the joining data is in the gigabyte or terabyte range, use either Bigtable or Cloud Storage to merge the joining data to the driving data, depending on the nature of the data.”
• Bigtable works with Managed Service for Apache Spark From the official documentation: “With Managed Service for Apache Spark, you can run Hadoop jobs that read from and write to Bigtable.”
• Cloud Storage works with Knowledge Catalog From the official documentation: “Knowledge Catalog is an intelligent governance solution for data and AI assets in Google Cloud. It provides a centralized inventory where you can discover, manage, and govern your data across Google Cloud data sources like BigQuery, Cloud Storage, Pub/Sub, and Spanner.”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• custom roles is part of Identity and Access Management From the official documentation: “To support this, IAM offers [custom roles](/iam/docs/creating-custom-roles).”
• Dataflow depends on Cloud Storage From the official documentation: “Begin by creating a Cloud Storage bucket using the Google Cloud console or Google Cloud CLI. The Dataflow pipeline uses this bucket as a temporary storage location.”
• Dataflow works with Google Cloud CLI From the official documentation: “Dataflow integrates with the Google Cloud CLI.”
• Dataflow is an alternative to Managed Service for Apache Spark From the official documentation: “For more complex data loads into your Cloud SQL for PostgreSQL database, consider using Dataflow or Managed Service for Apache Spark, which involves creating an ETL process.”
• Identity and Access Management (IAM) secures BigQuery From the official documentation: “BigQuery uses IAM for fine-grained access control.”
• Knowledge Catalog works with Pub/Sub From the official documentation: “Knowledge Catalog is an intelligent governance solution for data and AI assets in Google Cloud. It provides a centralized inventory where you can discover, manage, and govern your data across Google Cloud data sources like BigQuery, Cloud Storage, Pub/Sub, and Spanner.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with Cloud Storage bucket From the official documentation: “BigQuery lets you load [Datastore](/datastore) entities from a Cloud Storage bucket into a BigQuery table for analysis.”
• BigQuery is an alternative to Managed Service for Apache Spark From the official documentation: “An Analytics Workload refers to the migration of new Data Lake and Data Warehouse environments from on-premises (e.g., Teradata, Cloudera) and cloud platforms (e.g., Snowflake, Redshift, Databricks) to BigQuery or Managed Service for Apache Spark on Google Cloud.”
• BigQuery works with service account From the official documentation: “The service account can be used by services, such as Cloud Run, to read and modify data in the BigQuery dataset.”
• Bigtable is an alternative to Cloud SQL From the official documentation: “If you're interested in evaluating how the performance of your on-premises databases compares to [Cloud SQL](/sql), [Spanner](/spanner), [Firestore](/firestore), or [Bigtable](/bigtable), you could implement a PoC where the same business logic uses different databases.”
• Bigtable works with Cloud Storage From the official documentation: “For example, if you frequently write data to Bigtable from a Cloud Storage bucket in the `us-central1` (Iowa) region, create your Bigtable cluster in a zone within `us-central1`.”
• Bigtable works with Google Cloud CLI From the official documentation: “When you use the [gcloud CLI](/sdk/gcloud/reference/bigtable) to access Bigtable, you authenticate to Google Cloud as a principal, which provides the credentials used by the gcloud CLI commands.”
• Bigtable works with Identity and Access Management (IAM) From the official documentation: “Bigtable uses [IAM](/iam) for access control.”
• Bigtable works with Knowledge Catalog From the official documentation: “Knowledge Catalog automatically catalogs metadata about Bigtable resources.”
• Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud SQL works with Cloud Storage bucket From the official documentation: “If you exported into a Cloud Storage bucket, you can also check the log file created by Cloud SQL in the bucket for information about export status.”