Standard Tier

Related topics

• Standard Tier is part of Network Service Tiers From the official documentation: “Premium Tier delivers traffic on Google's premium backbone, while Standard Tier uses regular ISP networks.”
• Standard Tier is part of Security Command Center From the official documentation: “Security Command Center has three tiers: Standard, Premium, and Enterprise.”
• Standard Tier is part of Memorystore for Redis From the official documentation: “Memorystore for Redis supports Basic and Standard Tiers.”
• automatic failover is part of Standard Tier From the official documentation: “Standard Tier instances provide [High Availability](/memorystore/docs/redis/high-availability) using replication, read replicas, and automatic failover.”
• automatic failover works with Standard Tier From the official documentation: “The Standard Tier provides a highly available instance with multiple replicas, and enables fast recovery using automatic failover if the primary fails.”
• Basic Tier is an alternative to Standard Tier From the official documentation: “What is the difference between Basic Tier and Standard Tier for Memorystore for Redis?”
• RDB snapshots is part of Standard Tier From the official documentation: “To help protect your data and provide a baseline level of persistence, RDB snapshots for Standard Tier instances are enabled by default when you create a Memorystore for Redis instance using the Google Cloud console.”
• read replicas is part of Standard Tier From the official documentation: “The Standard Tier of Memorystore for Redis provides the ability to scale your application's read queries using read replicas.”
• 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.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Cloud Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• 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 Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Logging works with Security Command Center From the official documentation: “Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.”
• 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 Memorystore for Redis From the official documentation: “Additionally, integration with Cloud Monitoring makes it easy to monitor your Redis instances.”
• 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).)”
• Customer-Managed Encryption Keys secures GKE From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• Customer-Managed Encryption Keys works with Security Command Center From the official documentation: “to learn about using customer-managed encryption keys (CMEKs) with Security Command Center.”
• RDB snapshots is part of Memorystore for Redis From the official documentation: “This page gives an overview of RDB snapshots for Memorystore for Redis.”
• Basic Tier is part of Memorystore for Redis From the official documentation: “Memorystore for Redis supports Basic and Standard Tiers.”
• 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 Memorystore for Redis From the official documentation: “Redis produces logs that Cloud Logging captures.”
• Cloud Logging is an alternative to Security Command Center From the official documentation: “After you revoke compromised credentials and restore your service, review all access to your Google Cloud resources. You can use Cloud Logging or Security Command Center.”
• Cloud Monitoring works with RDB snapshots From the official documentation: “You can use [Cloud Monitoring](/memorystore/docs/redis/monitoring-instances) to view metrics for RDB snapshots.”
• Cloud Storage works with GKE From the official documentation: “This example configures GKE to store Pod snapshots in the `FOLDER_PATH/` path inside the Cloud Storage bucket `BUCKET_NAME`:”
• Cloud Storage works with read replicas From the official documentation: “The read replica or read pool uploads an output file to Cloud Storage.”
• 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 Storage From the official documentation: “[Cloud Storage](/storage/docs/introduction) provides features such as customer-managed encryption, lifecycle management, and aging and retention policies.”
• Customer-Managed Encryption Keys is part of Memorystore for Redis From the official documentation: “You can use CMEK on new Memorystore for Redis deployments only. You can't enable CMEK on existing Memorystore for Redis instances.”
• Customer-Managed Encryption Keys secures Security Command Center From the official documentation: “After you configure CMEK, Security Command Center encrypts data using your chosen Cloud KMS key.”
• GKE works with Memorystore for Redis From the official documentation: “You can only connect to your Redis instance from Google Kubernetes Engine clusters that use the same authorized network as the Redis instance.”
• Memorystore for Redis 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) - [Memorystore for Redis](/memorystore/docs/redis)”
• read replicas is part of Memorystore From the official documentation: “To use the read replicas feature for Memorystore for Redis your instance must have a CIDR IP address range of `/28` or greater.”
• read replicas is part of Memorystore for Redis From the official documentation: “Before you enable read replicas on an existing Memorystore for Redis instance, we strongly recommend that you reduce the write traffic to the primary node.”
• Security Command Center depends on Cloud Logging From the official documentation: “By using Security Command Center, you can see when high-risk threats such as malware, cryptomining, unauthorized access to Google Cloud resources, outgoing DDoS attacks, port scanning, and brute-force SSH have been detected based on your Cloud Logging logs.”
• Security Command Center secures Cloud Storage From the official documentation: “Security Command Center analyzes various logs for potential threats that affect Cloud Storage resources.”
• Security Command Center secures GKE From the official documentation: “Security Command Center performs [runtime](#runtime) and [log-based](#log-based) monitoring of Google Kubernetes Engine resources.”