Memorystore for Valkey

Related topics

• Memorystore for Memcached is an alternative to Memorystore for Valkey From the official documentation: “We recommend that you migrate your workloads to [Memorystore for Valkey](/memorystore/docs/valkey), which offers superior performance and features.”
• 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.”
• 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.”
• Cloud Key Management Service works with Memorystore for Valkey From the official documentation: “These values let Memorystore for Valkey instances use Cloud KMS keys only from the allowed organization, folder, or project.”
• Customer-Managed Encryption Keys works with Memorystore for Valkey From the official documentation: “You can use CMEK on new Memorystore for Valkey deployments only.”
• Cloud Audit Logs works with Memorystore for Valkey From the official documentation: “This document describes the audit logs created by Memorystore for Valkey as part of [Cloud Audit Logs](/logging/docs/audit).”
• Cloud Interconnect works with Memorystore for Valkey From the official documentation: “This diagram shows an example of a client connecting to Memorystore for Valkey from an on-premises network using Cloud Interconnect and Cloud Router.”
• Cloud Logging works with Memorystore for Valkey From the official documentation: “This page describes how to find and use [Cloud Logging](/logging/docs) to query and view maintenance logs for a Memorystore for Valkey instance.”
• Cloud Run works with Memorystore for Valkey From the official documentation: “The Cloud Run service can cache data in the Memorystore for Valkey instance.”
• Cloud Storage works with Memorystore for Valkey From the official documentation: “Memorystore for Valkey must have permission to access the destination Cloud Storage bucket.”
• Customer-Managed Encryption Keys secures Memorystore for Valkey From the official documentation: “CMEK lets you use your cryptographic keys to protect stored data in Memorystore for Valkey instances.”
• Google Cloud console works with Memorystore for Valkey From the official documentation: “If you are using the [Google Cloud console](https://console.cloud.google.com/), the console sends requests to Memorystore for Valkey on your behalf and handles any necessary backoff.”
• Identity and Access Management secures Memorystore for Valkey From the official documentation: “Management of Memorystore for Valkey instances is secured using Identity and Access Management (IAM) role-based access control.”
• VPC Service Controls secures Memorystore for Valkey From the official documentation: “You can protect your Memorystore for Valkey instances using VPC Service Controls.”
• 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”
• Customer-Managed Encryption Keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
• 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 Key Management Service works with Customer-Managed Encryption Keys From the official documentation: “With CMEK, Cloud Key Management Service wraps your stored volume keys.”
• 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.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• Cloud Run works with Eventarc From the official documentation: “Create a Cloud Run service as an event destination for the Eventarc trigger:”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• 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 Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• Cloud Storage works with Eventarc From the official documentation: “Trigger functions from Cloud Storage using Eventarc”
• Customer-Managed Encryption Keys is part of Cloud Key Management Service From the official documentation: “The Cloud KMS keys that you create are customer-managed keys.”
• Cloud Audit Logs works with Cloud Key Management Service From the official documentation: “Cloud Audit Logs for Cloud KMS in the Activity stream read like generic logs, and are not easily read by a human.”
• 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 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 works with Eventarc From the official documentation: “Eventarc triggers Cloud Run functions when a particular event occurs in BigQuery.”
• 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.”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• BigQuery works with Cloud Key Management Service From the official documentation: “A Cloud KMS key is considered available and accessible by BigQuery under the following conditions:”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• 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:”
• 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.”
• 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.”
• 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 Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
• 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 Eventarc From the official documentation: “Eventarc automatically sends audit logs to Cloud Logging for troubleshooting and streams metrics to Cloud Monitoring for trend analysis and alerting.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Cloud Run functions From the official documentation: “This hands-on lab shows you how to view your Cloud Run functions with their execution times, execution counts, and memory usage in the Google Cloud console. These metrics are also available in Cloud Monitoring.”
• 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 Monitoring works with Memorystore for Memcached From the official documentation: “Auto-generated ID of the Memcached node used to view node-level metrics in Cloud Monitoring.”
• 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 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).)”