Google APIs Discovery Service

Related topics

• Alerting works with Google APIs Discovery Service From the official documentation: “The discovery service helps you get a broad view of your data and enable [alerting](/sensitive-data-protection/docs/dp-receive-pubsub-messages), [reporting](/sensitive-data-protection/docs/analyze-data-profiles), and…”
• BigQuery works with Google APIs Discovery Service From the official documentation: “For example, a discovery scan of BigQuery or Cloud SQL data generates data profiles at the project, table, and column levels.”
• client libraries works with Google APIs Discovery Service From the official documentation: “For client libraries that use the Google APIs Discovery Service, use the API name `sqladmin` to build a client.”
• Cloud SQL works with Google APIs Discovery Service From the official documentation: “For example, a discovery scan of BigQuery or Cloud SQL data generates data profiles at the project, table, and column levels.”
• Google APIs Discovery Service works with remediation From the official documentation: “The discovery service helps you get a broad view of your data and enable [alerting](/sensitive-data-protection/docs/dp-receive-pubsub-messages), [reporting](/sensitive-data-protection/docs/analyze-data-profiles), and…”
• 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”
• Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• 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.”
• Customer-Managed Encryption Keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using 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 secures Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Customer-Managed Encryption Keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• BigQuery works with Spanner From the official documentation: “Federated analytics seamlessly combine data from Spanner and other sources in BigQuery.”
• Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, 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 Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• Spanner depends on Application Default Credentials From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Customer-Managed Encryption Keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
• Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Cloud Monitoring works with Spanner From the official documentation: “Monitor Spanner metrics using Cloud Monitoring.”
• Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
• Application Default Credentials works with Cloud SQL From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
• 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).”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
• 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 Customer-Managed Encryption Keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
• Cloud SQL is an alternative to Spanner From the official documentation: “If a workload requires transaction processing with strong relational consistencies, [Spanner](/spanner/docs/overview) or [Cloud SQL](/sql/docs) can be better alternatives.”
• Customer-Managed Encryption Keys depends on Cloud Storage From the official documentation: “If used for storing Customer-managed Encryption Keys (CMEK): Cloud Storage (See [Cloud Storage pricing](/storage/pricing).)”
• Alerting is part of Cloud Monitoring From the official documentation: “You can access this alerting policy from the **Alerting** tab in the Monitoring UI.”
• Application Default Credentials is part of client libraries From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
• Application Default Credentials works with client libraries From the official documentation: “Client libraries can use [Application Default Credentials](/docs/authentication/application-default-credentials) to easily authenticate with Google APIs and send requests to those APIs.”
• Application Default Credentials configures client libraries 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 Cloud Logging From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
• 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.”
• client libraries works with Cloud SQL From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
• client libraries works with 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).”
• client libraries is part of Spanner From the official documentation: “Spanner provides a set of [Client libraries](/spanner/docs/reference/libraries) for various languages, and the ability to read and write data using Spanner-specific API calls, as well as by using [SQL queries](/spanner/docs/query-syntax) and [Data Modification Language…”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• Cloud Logging depends on Customer-Managed Encryption Keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Cloud Logging works with Spanner From the official documentation: “Both Spanner and Agent Platform provide monitoring dashboards and write logs to Cloud Logging, which can contain additional details.”
• 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 Storage works with Spanner From the official documentation: “Move Spanner databases to and from Avro or CSV files stored in Cloud Storage.”
• Customer-Managed Encryption Keys is part of BigQuery From the official documentation: “If you require more control over encryption keys, BigQuery supports [customer-managed encryption keys](/bigquery/docs/customer-managed-encryption) in the [Cloud Key Management Service](/kms/docs).”
• Customer-Managed Encryption Keys configures Cloud Logging From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Customer-Managed Encryption Keys secures Cloud Logging From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Customer-Managed Encryption Keys is part of Cloud SQL From the official documentation: “Cloud SQL also lets you add another layer of encryption to data using [customer-managed encryption keys (CMEK)](/sql/docs/postgres/cmek).”
• Customer-Managed Encryption Keys is part of Cloud Storage From the official documentation: “[Cloud Storage](/storage/docs/introduction) provides features such as customer-managed encryption, lifecycle management, and aging and retention policies.”