Memorystore for Redis Cluster

Related topics

• Cloud Monitoring works with Memorystore for Redis Cluster From the official documentation: “This section lists and describes Cloud Monitoring metrics that are available for Memorystore for Redis Cluster.”
• Customer-Managed Encryption Keys works with Memorystore for Redis Cluster From the official documentation: “You can use CMEK on new Memorystore for Redis Cluster deployments only.”
• Memorystore for Redis Cluster works with service account From the official documentation: “The service account can manage the Memorystore for Redis Cluster.”
• AOF persistence is part of Memorystore for Redis Cluster From the official documentation: “This page provides an overview of Append-Only File (AOF) persistence for Memorystore for Redis Cluster.”
• Cloud Audit Logs works with Memorystore for Redis Cluster From the official documentation: “This document describes the audit logs created by Memorystore for Redis Cluster as part of [Cloud Audit Logs](/logging/docs/audit).”
• Cloud Logging works with Memorystore for Redis Cluster From the official documentation: “Memorystore for Redis Cluster produces logs that Cloud Logging captures.”
• Cloud Run works with Memorystore for Redis Cluster From the official documentation: “The Cloud Run service can cache data in the Memorystore for Redis Cluster.”
• Cloud Storage works with Memorystore for Redis Cluster From the official documentation: “To seed a cluster from RDB files in a Cloud Storage bucket, you must grant Memorystore for Redis Cluster access to the bucket and objects, and then import the data from the files.”
• Compute Engine works with Memorystore for Redis Cluster From the official documentation: “You can connect to the Memorystore for Redis Cluster instance from any Compute Engine VM that uses the Memorystore instance's authorized network.”
• GKE Enterprise works with Memorystore for Redis Cluster From the official documentation: “For example, if you're using Memorystore for Redis Cluster with Google Kubernetes Engine (GKE) Enterprise edition (GKE Enterprise), then you can customize the predefined dashboard.”
• Identity and Access Management secures Memorystore for Redis Cluster From the official documentation: “Management of clusters is secured using Identity and Access Management (IAM) role-based access control.”
• Memorystore for Redis Cluster is part of Memorystore From the official documentation: “We offer the following Memorystore database services: - [Memorystore for Valkey](/memorystore/docs/valkey) - [Memorystore for Redis Cluster](/memorystore/docs/cluster)”
• 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.”
• 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.”
• 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.”
• 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.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• Cloud Run functions works with Pub/Sub From the official documentation: “Use Cloud Run functions to publish messages on Pub/Sub.”
• 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.”
• Customer-Managed Encryption Keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• 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.”
• Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
• Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• 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 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.”
• Cloud Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• 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 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.”
• 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 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.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• 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.”
• Customer-Managed Encryption Keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• 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 Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Monitoring works with Memorystore for Valkey From the official documentation: “This section lists and describes Cloud Monitoring metrics that are available for Memorystore for Valkey.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run works with Google Kubernetes Engine From the official documentation: “Connecting Cloud Run services to Cloud Service Mesh lets you securely route traffic to workloads on GKE.”
• 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:”
• Compute Engine is an alternative to Google Kubernetes Engine From the official documentation: “You can install MongoDB on a Compute Engine instance or you can deploy MongoDB on Google Kubernetes Engine.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• AOF persistence works with Cloud Monitoring From the official documentation: “You can use [Cloud Monitoring](/memorystore/docs/valkey/monitor-instances) to view metrics for AOF persistence.”
• AOF persistence is part of Memorystore for Valkey From the official documentation: “This page provides an overview of Append Only File (AOF) persistence for Memorystore for Valkey.”
• 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 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 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 Google Kubernetes Engine From the official documentation: “By default, GKE clusters send system log data and system metric data to Logging and Monitoring.”