IAM roles and permissions

Related topics

• Filestore depends on IAM roles and permissions From the official documentation: “Learn about the [IAM roles and permissions](/filestore/docs/iam) needed to use Filestore.”
• Google Cloud CLI configures IAM roles and permissions From the official documentation: “You can grant and manage IAM roles using the Google Cloud console, the IAM API methods, or the Google Cloud CLI.”
• Google Cloud console configures IAM roles and permissions From the official documentation: “You can grant and manage IAM roles using the Google Cloud console, the IAM API methods, or the Google Cloud CLI.”
• IAM roles and permissions is part of Cloud Key Management Service From the official documentation: “This page lists the IAM roles and permissions for Cloud Key Management Service.”
• IAM roles and permissions secures Error Reporting From the official documentation: “IAM roles and permissions determine which Error Reporting resources you can access through the Google Cloud console and the [Error Reporting API](/error-reporting/reference/rest).”
• IAM roles and permissions configures service account From the official documentation: “[Create a service account](/iam/docs/service-accounts-create) that has the following Identity and Access Management (IAM) roles and permissions:”
• Google Cloud CLI is an alternative to Google Cloud console From the official documentation: “You can use the console or the Google Cloud CLI to change the settings.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Application Default Credentials secures Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Compute Engine works with service account From the official documentation: “A common method is to attach a service account to a resource like a Compute Engine instance.”
• Application Default Credentials secures Cloud Run functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
• Cloud Storage works with Google Cloud CLI From the official documentation: “The gcloud CLI is the preferred command line tool for accessing Cloud Storage.”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Application Default Credentials works with Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Cloud Run depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Google Cloud CLI configures Application Default Credentials From the official documentation: “To configure ADC with a user account, you use the Google Cloud CLI:”
• Spanner depends on Application Default Credentials From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Cloud Run functions works with Cloud Storage From the official documentation: “(GCF translates GCS notifications to HTTP requests internally)”
• Cloud Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
• Application Default Credentials works with Cloud Key Management Service From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run functions depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
• Cloud Run functions works with Spanner From the official documentation: “Using Spanner with Cloud Run functions (1st gen)”
• Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Compute Engine works with Google Cloud CLI From the official documentation: “Some applications might use commands from the gcloud CLI, which is included by default in most Compute Engine images.”
• Application Default Credentials configures Cloud Run functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
• Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
• Application Default Credentials works with Google Cloud CLI From the official documentation: “To do so, provide your user credentials to ADC by using the Google Cloud CLI.”
• Application Default Credentials works with service account From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
• Cloud Key Management Service works with Google Cloud CLI From the official documentation: “To use Cloud KMS on the command line, first [Install or upgrade to the latest version of Google Cloud CLI](/sdk/install).”
• Cloud Key Management Service works with service account From the official documentation: “When your Database Migration Service migration jobs have CMEK enabled, you need to use a service account to request key access from Cloud Key Management Service.”
• Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Run works with Filestore From the official documentation: “Using Filestore with Cloud Run Learn how to use Filestore network file system from a Cloud Run service.”
• Cloud Run functions depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• Compute Engine works with Error Reporting From the official documentation: “To use Error Reporting with Compute Engine VM instances, do the following:”
• Compute Engine works with Filestore From the official documentation: “Filestore instances are fully managed file servers on Google Cloud that can be connected to a number of client types: - [Compute Engine VMs](/filestore/docs/mounting-fileshares)”
• Google Cloud CLI depends on Application Default Credentials From the official documentation: “To authenticate with the gcloud CLI, generate a local Application Default Credentials (ADC) file by running this command.”
• Google Cloud CLI works with Spanner From the official documentation: “You have already set up [gcloud CLI](/sdk/docs) for use with Spanner.”
• Application Default Credentials configures Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Application Default Credentials configures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Application Default Credentials is an alternative to Google Cloud CLI From the official documentation: “You can authenticate to [the Vision API](/vision/docs/reference/rest) by using your [gcloud CLI credentials](/sdk/docs/authenticate) or by using [Application Default Credentials](/docs/authentication/application-default-credentials).”
• Application Default Credentials depends on service account From the official documentation: “If your `BidiProcessOrder` client runs in a secure environment that can be configured with service account credentials (such as Compute Engine, Google Kubernetes Engine, or your on-premise servers), it can use [Application Default Credentials…”
• Application Default Credentials is an alternative to service account From the official documentation: “There are two ways to obtain credentials for the agent to use: - Let the agent use a service account with private-key authentication - Let the agent use application default credentials (ADC).”
• Cloud Key Management Service depends on Application Default Credentials From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Cloud Key Management Service secures Cloud Run functions From the official documentation: “[Cloud Key Management Service (Cloud KMS)](/kms) stores the [customer-managed encryption keys (CMEKs)](/kms/docs/cmek) that are used by the services in this blueprint, including your serverless application, Artifact Registry, and Cloud Run functions.”
• Cloud Key Management Service depends on Google Cloud CLI From the official documentation: “To use Cloud KMS on the command line, first [Install or upgrade to the latest version of Google Cloud CLI](/sdk/install).”
• Cloud Key Management Service works with Google Cloud console From the official documentation: “There is also a web-based interface for [Cloud KMS on the Google Cloud console](https://console.cloud.google.com/security/kms), which allows for key management operations.”
• Cloud Key Management Service depends on Spanner From the official documentation: “Cloud KMS stores all of its data and metadata in Spanner databases which provide high data durability and availability with synchronous replication.”
• Cloud Key Management Service works with Spanner From the official documentation: “After the database is created, Spanner calls Cloud KMS about every five minutes to make sure that the key is still valid.”
• Cloud Run is an alternative to Cloud Run functions From the official documentation: “The blueprint supports the following use cases: - Deploying a serverless architecture using Cloud Run functions (this document) - [Deploying a serverless architecture using Cloud Run](/architecture/blueprints/serverless-blueprint)”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run works with Error Reporting From the official documentation: “Cloud Run is configured to use Error Reporting automatically.”
• Cloud Run works with Google Cloud CLI From the official documentation: “Google Cloud CLI contains a [local development environment](/sdk/gcloud/reference/beta/code/dev) for emulating Cloud Run that can build a container from source, run the container on your local machine, and automatically rebuild the container upon source code changes.”
• Cloud Run works with service account From the official documentation: “Map a custom Service Account to a Cloud Run service”
• Cloud Run works with Spanner From the official documentation: “Use Spanner [client libraries](/spanner/docs/reference/libraries) from Cloud Run.”
• Cloud Run functions is part of Cloud Run From the official documentation: “| Cloud Run functions | Standalone functions on Cloud Run. |”