Identity and Access Management (IAM)

Related topics

• Identity and Access Management (IAM) secures BigQuery From the official documentation: “BigQuery uses IAM for fine-grained access control.”
• AlloyDB for PostgreSQL works with Identity and Access Management (IAM) From the official documentation: “Provide Google Cloud integrations for [Identity and Access Management (IAM)](/alloydb/docs/manage-iam-authn), [tags](/alloydb/docs/manage-tags), [Cloud Key Management Service](/alloydb/docs/cmek), and [Network Intelligence Center](/network-intelligence-center/docs).”
• Artifact Analysis depends on Identity and Access Management (IAM) From the official documentation: “Artifact Analysis uses [Identity and Access Management (IAM)](/iam/docs/overview) to grant granular access to specific resources depending on the task you are going to perform.”
• Cloud Logging depends on Identity and Access Management (IAM) From the official documentation: “Cloud Logging uses [Identity and Access Management (IAM)](/iam/docs/overview) roles and permissions to let you control who can view, write, and manage Logging resources.”
• Cloud Profiler works with Identity and Access Management (IAM) From the official documentation: “Cloud Profiler controls access to profiling activities in Google Cloud projects by using [Identity and Access Management (IAM)](/iam/docs/overview) roles and permissions.”
• 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.”
• Identity and Access Management (IAM) secures Cloud Deploy From the official documentation: “Access in Cloud Deploy is controlled using [Identity and Access Management (IAM)](/iam).”
• Identity and Access Management (IAM) secures Cloud Storage From the official documentation: “Cloud Storage supports two methods for granting users access to your buckets and objects: Identity and Access Management (IAM) and access control lists (ACLs).”
• Identity and Access Management (IAM) secures Cloud Trace From the official documentation: “Cloud Trace uses Identity and Access Management (IAM) to control access to resources.”
• Identity and Access Management (IAM) secures Error Reporting From the official documentation: “You can use [Identity and Access Management (IAM)](/iam/docs/overview) roles to control access to Error Reporting data, ensuring team members have the permissions they need to view, triage, and manage application errors while enforcing least privilege.”
• Identity and Access Management (IAM) secures Pub/Sub From the official documentation: “Pub/Sub uses [Identity and Access Management (IAM)](/iam) for access control.”
• 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 Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Cloud Deploy works with Cloud Run From the official documentation: “Quickstart: Deploy an app to Cloud Run by using Cloud Deploy”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Run functions works with Pub/Sub From the official documentation: “Use Cloud Run functions to publish messages on Pub/Sub.”
• BigQuery works with Cloud Run functions From the official documentation: “Learn how to write an HTTP Cloud Run function that submits a query to BigQuery.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• 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 Audit Logs works with Cloud Storage From the official documentation: “This page provides supplemental information for using [Cloud Audit Logs](/logging/docs/audit) with Cloud Storage.”
• Cloud Audit Logs works with VPC Service Controls From the official documentation: “VPC Service Controls integrate with Cloud Audit Logs to monitor access to the control plane.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Run functions works with Cloud Storage From the official documentation: “(GCF translates GCS notifications to HTTP requests internally)”
• Cloud Run functions depends on Pub/Sub From the official documentation: “The Pub/Sub message triggers Cloud Run functions.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• 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.”
• Cloud Deploy works with Cloud Storage From the official documentation: “Delete the Cloud Storage buckets that Cloud Deploy created.”
• Cloud Logging works with Error Reporting From the official documentation: “To connect your EC2 applications to Error Reporting, send your exceptions or other errors to Logging.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• 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.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• AlloyDB for PostgreSQL works with BigQuery From the official documentation: “Datastream lets you stream from AlloyDB for PostgreSQL to BigQuery using the Free Tier, providing up to 100 GiB of change data capture data free every month.”
• AlloyDB for PostgreSQL works with Cloud Storage From the official documentation: “AlloyDB lets you import data from files located in a Cloud Storage bucket.”
• Artifact Analysis secures Cloud Run From the official documentation: “To identify and mitigate security risks in the container images, use Artifact Analysis to automatically run vulnerability scans.”
• Artifact Analysis works with VPC Service Controls From the official documentation: “VPC Service Controls provides support for Artifact Analysis.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Cloud Audit Logs works with Pub/Sub From the official documentation: “Working with audit logs Learn about the default and optional logs created by Pub/Sub as part of Cloud Audit Logs”
• Cloud Deploy works with GKE From the official documentation: “Quickstart: Deploy an app to GKE by using Cloud Deploy”
• Cloud Deploy depends on Pub/Sub From the official documentation: “Cloud Deploy uses Pub/Sub to publish notifications for two purposes:”
• Cloud Deploy works with Pub/Sub From the official documentation: “Cloud Deploy publishes operational messages to Pub/Sub.”
• Cloud Logging works with Cloud Run functions From the official documentation: “Cloud Run functions is configured to use Cloud Logging automatically.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• Cloud Logging works with Cloud Trace From the official documentation: “To identify requests with high latency using Cloud Logging, apply the `traceSampled=true` filter to correlate logs in Cloud Logging with traces in Cloud Trace.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• GKE works with Pub/Sub From the official documentation: “GKE publishes upgrade notifications to [Pub/Sub](/pubsub/docs/overview), providing you with a channel to receive information from GKE about your clusters.”
• Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
• AlloyDB for PostgreSQL works with Cloud Audit Logs From the official documentation: “To monitor administrative and data access operations on your AlloyDB for PostgreSQL clusters, instances, and backups, you can view and configure Cloud Audit Logs for AlloyDB.”
• AlloyDB for PostgreSQL works with GKE From the official documentation: “Connect from Google Kubernetes Engine (GKE) to AlloyDB”
• AlloyDB for PostgreSQL works with Identity and Access Management From the official documentation: “The AlloyDB Auth Proxy and AlloyDB Language Connectors let you use [Identity and Access Management](/iam/docs/overview) (IAM) to control who has access to your data.”
• AlloyDB for PostgreSQL works with Pub/Sub From the official documentation: “Enabling the integration activates the export of AlloyDB metadata—such as databases, schemas, and tables—to Cloud Storage buckets for periodic sync or to Pub/Sub topics for near real-time sync, making it available to Knowledge Catalog.”