Meta tags:

Headings (most frequently used words):

create, and, instance, console, gcloud, instances, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, before, you, begin, set, up, networking, an, single, zone, other, prerequisites, products, pricing, support, resources, engage,

Text of the page (most frequently used words):
the (227), cluster (104), for (91), you (78), and (66), redis (57), memorystore (47), select (42), #create (37), your (36), #instance (33), cloud (30), want (28), google (26), node (26), with (25), section (25), zone (24), that (24), type (23), then (23), use (22), this (21), network (21), from (20), project (19), management (18), pool (18), about (17), networking (17), data (16), using (16), region (16), encryption (16), must (15), maintenance (15), following (14), iam (14), replicas (13), persistence (13), only (12), default (12), number (12), service (12), key (12), set (11), shard (11), count (11), menu (11), backups (11), enable (11), certificate (11), manage (10), see (10), more (10), single (10), gcloud (10), option (10), checkbox (10), managed (10), add (10), information (9), per (9), policy (9), can (9), authority (9), resources (8), determines (8), recommend (8), another (8), shared (8), used (8), lowercase (8), application (8), enter (8), days (8), before (8), kms (8), customer (8), access (8), overview (8), instances (8), code (7), thumb (7), are (7), capacity (7), specification (7), connection (7), start (7), clusters (7), one (7), they (7), cmek (7), security (7), console (7), supported (7), page (6), total (6), development (6), run (6), letter (6), replica (6), specify (6), options (6), multiple (6), authentication (6), commands (6), vpc (6), samples (5), where (5), mode (5), multi (5), values (5), because (5), networks (5), automatically (5), these (5), transit (5), note (5), applications (5), connect (5), steps (5), api (5), search (5), cross (5), português (4), español (4), down (4), need (4), shards (4), memory (4), storing (4), shard_count (4), testing (4), purposes (4), has (4), sla (4), production (4), environment (4), core (4), nano (4), caution (4), node_type (4), replica_count (4), region_id (4), creating (4), letters (4), numbers (4), hyphens (4), instance_id (4), click (4), when (4), window (4), time (4), daily (4), field (4), value (4), automated (4), rdb (4), aof (4), private (4), begin (4), regions (4), roles (4), cli (4), guides (4), tools (4), vector (4), scale (4), all (3), other (3), otherwise (3), content (3), registered (3), its (3), lets (3), accepted (3), fails (3), projects (3), global (3), command (3), custom (3), secure (3), keep (3), how (3), keys (3), such (3), resource (3), which (3), selecting (3), zonal (3), availability (3), complete (3), instructions (3), available (3), compute (3), solutions (3), unavailable (3), distributed (3), basic (3), role (3), databases (3), monitoring (3), monitor (3), replication (3), quickstart (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), terms (2), site (2), youtube (2), started (2), support (2), pricing (2), products (2), understand (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), under (2), details (2), license (2), send (2), feedback (2), nodes (2), distribution (2), provisioning (2), zone_distribution_mode (2), format (2), here (2), match (2), operation (2), network_project_id (2), network_id (2), placed (2), characters (2), end (2), replace (2), customize (2), schedule (2), align (2), needs (2), minimize (2), disruptions (2), day (2), occur (2), hour (2), updates (2), routinely (2), ensure (2), reliable (2), performant (2), date (2), backup (2), deleted (2), 365 (2), retain (2), persist (2), acceptable (2), database (2), append (2), file (2), strategy (2), cmeks (2), integrated (2), services (2), encrypt (2), located (2), same (2), text (2), collection (2), cas (2), common (2), issuance (2), identity (2), makes (2), rotation (2), easier (2), achieve (2), higher (2), effective (2), queries (2), second (2), qps (2), represent (2), hierarchy (2), issue (2), digital (2), certificates (2), modes (2), selects (2), displayed (2), credentials (2), confidential (2), transmitted (2), encrypts (2), tls (2), increase (2), auth (2), specifications (2), size (2), also (2), unique (2), name (2), sections (2), important (2), provides (2), not (2), list (2), plan (2), terraform (2), created (2), zones (2), after (2), follow (2), procedure (2), have (2), editor (2), owner (2), admin (2), consumer (2), connectivity (2), make (2), sure (2), version (2), billing (2), enabled (2), selector (2), delete (2), based (2), documentation (2), sdk (2), languages (2), frameworks (2), infrastructure (2), costs (2), usage (2), storage (2), observability (2), migration (2), industry (2), hybrid (2), multicloud (2), analytics (2), pipelines (2), hosting (2), high (2), issues (2), troubleshoot (2), metrics (2), logs (2), view (2), info (2), control (2), configure (2), client (2), library (2), connections (2), best (2), practices (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, action, join, cookies, privacy, tech, twitter, events, blog, engage, training, certification, architecture, center, getting, github, system, status, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, noted, java, trademark, oracle, affiliates, developers, policies, apache, creative, commons, attribution, provision, flag, applicable, choose, between, disabled, authorized, alpha, central1, 335118, highmem, medium, example, currently, shows, deploy, both, setup, choice, along, clients, engine, vms, simplified, configuration, tip, without, creates, allocation, temporary, becomes, redistributes, evenly, among, hasn, been, will, guidance, read, determine, predefined, prerequisites, installed, previously, latest, running, least, 440, components, update, initialize, install, learn, check, don, instead, existing, finish, removing, associated, save, categorize, preferences, stay, organized, collections, home, isn, utilization, expensive, address, health, audit, self, simulate, find, windows, build, llm, powered, langchain, integrate, technologies, json, features, limitations, query, syntax, indexing, vectors, dropindex, _list, generative, back, constraints, controls, token, configurations, prevent, deletion, work, secondary, scaling, provisioned, user, vpcs, get, environments, blocked, operational, guidelines, discover, free, skip, main,

Text of the page (random words):
n instructions in the google cloud console on the project selector page select or create a google cloud project note if you don t plan to keep the resources that you create in this procedure create a project instead of selecting an existing project after you finish these steps you can delete the project removing all resources associated with the project go to project selector make sure that billing is enabled for your project learn how to check if billing is enabled on a project install and initialize the google cloud cli note if you installed the gcloud cli previously make sure you have the latest version by running gcloud components update you need at least gcloud cli version 440 0 0 to access the memorystore for redis cluster gcloud cli commands enable the memorystore for redis api memorystore for redis enable the network connectivity api network connectivity api enable the service consumer management api service consumer management api other prerequisites you must have one of these iam roles in the google cloud project you re using roles redis admin the memorystore admin predefined iam role roles owner the owner basic iam role roles editor the editor basic iam role set up networking read the networking page to determine if you need to set up a service connection policy if a service connection policy hasn t been created for the network with which you will create the redis cluster follow the networking guidance to create it create an instance important before you follow the steps in this procedure complete the steps in the before you begin and set up networking sections if you create a cluster with replicas and a single zone of the region where you want the cluster to be created is unavailable then memorystore for redis cluster creates the cluster in the available zones of the region this zonal allocation is temporary after the unavailable zone becomes available memorystore for redis cluster redistributes the nodes of the cluster so that they re evenly distributed among the zones if you create a cluster without replicas and a single zone is unavailable then memorystore for redis cluster fails to create the cluster tip if you plan on using private networking then you can deploy both the private networking setup of your choice and the memorystore for redis cluster instance along with clients such as compute engine vms by using terraform for more information see simplified cloud networking configuration solutions console in the google cloud console go to the memorystore for redis cluster page memorystore for redis cluster click create cluster in the name your cluster instance section enter an id for the cluster the cluster id must use only lowercase letters numbers and hyphens it must also start with a letter and be unique in its region from the region menu select a region for your cluster in the zonal availability section select the multi zone option because you want to create a multi zone cluster in the node type section select a node type caution we recommend that you use the redis shared core nano node type only for development or testing purposes because this node type has no sla if you run memorystore for redis cluster in a production environment then we recommend using another node type in the cluster size section enter the number of shards for your cluster the shard count determines the total memory capacity for storing cluster data for more information about cluster specifications see cluster and node specification if you want to create a cluster with replicas then in the replicas section select the number of replicas per shard you can select 0 5 replicas the default value is 1 replica in the set up connection section select the network that your applications can use to connect to this cluster for more information about private networking for memorystore for redis cluster see networking overview if you want to increase the security of your cluster then in the security section enable iam authentication by selecting the enable iam auth checkbox note if you select this checkbox then memorystore for redis cluster selects the enable in transit encryption tls checkbox automatically and the certificate authority management section is displayed memorystore for redis cluster encrypts your credentials so that they re confidential when they re transmitted from the instance to the application in the certificate authority management section select the per instance ca customer managed ca or shared ca option these options represent the certificate authority ca modes for your cluster the ca mode determines which ca hierarchy is used to issue the digital certificates for the cluster if you select the customer managed ca option then you must add a ca pool a ca pool is a collection of multiple cas with a common certificate issuance policy and identity and access management iam policy a ca pool makes ca rotation management easier and lets you achieve higher total effective queries per second qps to add a ca pool do one of the following to add a ca pool from another google cloud project select the add ca from another project checkbox and then enter the resource id for the pool in the text field to add a ca pool that s located in the same google cloud project as the project that you re using to create the cluster select the pool from the ca pool menu in the encryption section select one of the following options google managed encryption key you want google to use a key to encrypt the data in the cluster this is google default encryption cloud kms key you want to manage the encryption of your data by using customer managed encryption keys cmeks in cloud key management service cloud kms with cmek integrated services such as memorystore for redis cluster if you select this option then do the following from the key management type menu select cloud kms from the select a cloud kms key menu select a cmek in the data persistence strategy section specify how you want memorystore for redis cluster to persist the data in your cluster acceptable values are no persistence append only file aof persistence and redis database rdb persistence if you want to enable automated backups for your cluster then do the following select the automated daily backups checkbox in the days to retain backups field enter the number of days that you want memorystore for redis cluster to keep backups before they re deleted automatically you can specify from 1 to 365 days the default value is 35 days from the time window menu select a time for the daily backup in the maintenance section select one of the following options default memorystore for redis cluster updates your cluster routinely to ensure that the service is reliable performant secure and up to date custom you want to customize the maintenance schedule for your cluster to align with your application s needs and to minimize disruptions if you select this option then specify the day that you want maintenance to occur and the hour when you want the maintenance window to start click create cluster gcloud to create a memorystore for redis cluster instance run the create command gcloud redis clusters create instance_id region region_id network network replica count replica_count node type node_type shard count shard_count replace the following instance_id is the id of the memorystore for redis cluster instance you re creating your instance id must be 1 to 63 characters and use only lowercase letters numbers or hyphens it must start with a lowercase letter and end with a lowercase letter or number region_id is the region where you want the instance placed note you can only create instances in the supported regions for memorystore for redis cluster not all of the regions currently supported by memorystore for redis are available for memorystore for redis cluster the gcloud redis regions list commands shows supported regions for memorystore for redis not memorystore for redis cluster network is the network used to create your instance it must use the format projects network_project_id global networks network_id the network id used here must match the network id used by the service connection policy otherwise the create operation fails replica_count is the number of replicas per shard accepted values are 0 5 node_type is the node type that you want to use for the cluster caution we recommend that you use the redis shared core nano node type only for development or testing purposes because this node type has no sla if you run memorystore for redis cluster in a production environment then we recommend using another node type shard_count determines the number of shards in your instance shard count determines the total memory capacity for storing cluster data to see more details about cluster specification see cluster and node specification for example gcloud alpha redis clusters create my instance region us central1 network projects my project 335118 global networks default replica count 2 node type redis highmem medium shard count 8 by default in transit encryption is disabled and the authorized network is default create a single zone instance this section provides instructions on creating a single zone instance important before following these steps complete the steps in the before you begin and set up networking sections console in the google cloud console go to the memorystore for redis cluster page memorystore for redis cluster click create cluster in the name your cluster instance section enter an id for the cluster the cluster id must use only lowercase letters numbers and hyphens it must also start with a letter and be unique in its region from the region menu select a region for your cluster in the zonal availability section do the following select the single zone option from the zone menu select the zone where you want memorystore for redis cluster to create the cluster in the node type section select a node type caution we recommend that you use the redis shared core nano node type only for development or testing purposes because this node type has no sla if you run memorystore for redis cluster in a production environment then we recommend using another node type in the cluster size section enter the number of shards for your cluster the shard count determines the total memory capacity for storing cluster data for more information about cluster specifications see cluster and node specification if you want to create a cluster with replicas then in the replicas section select the number of replicas per shard you can select 0 5 replicas the default value is 1 replica in the set up connection section select the network that your applications can use to connect to this cluster for more information about private networking for memorystore for redis cluster see networking overview if you want to increase the security of your cluster then in the security section enable iam authentication by selecting the enable iam auth checkbox note if you select this checkbox then memorystore for redis cluster selects the enable in transit encryption tls checkbox automatically and the certificate authority management section is displayed memorystore for redis cluster encrypts your credentials so that they re confidential when they re transmitted from the instance to the application in the certificate authority management section select the per instance ca customer managed ca or shared ca option these options represent the certificate authority ca modes for your cluster the ca mode determines which ca hierarchy is used to issue the digital certificates for the cluster if you select the customer managed ca option then you must add a ca pool a ca pool is a collection of multiple cas with a common certificate issuance policy and identity and access management iam policy a ca pool makes ca rotation management easier and lets you achieve higher total effective queries per second qps to add a ca pool do one of the following to add a ca pool from another google cloud project select the add ca from another project checkbox and then enter the resource id for the pool in the text field to add a ca pool that s located in the same google cloud project as the project that you re using to create the cluster select the pool from the ca pool menu in the encryption section select one of the following options google managed encryption key you want google to use a key to encrypt the data in the cluster this is google default encryption cloud kms key you want to manage the encryption of your data by using customer managed encryption keys cmeks in cloud key management service cloud kms with cmek integrated services such as memorystore for redis cluster if you select this option then do the following from the key management type menu select cloud kms from the select a cloud kms key menu select a cmek in the data persistence strategy section specify how you want memorystore for redis cluster to persist the data in your cluster acceptable values are no persistence append only file aof persistence and redis database rdb persistence if you want to enable automated backups for your cluster then do the following select the automated daily backups checkbox in the days to retain backups field enter the number of days that you want memorystore for redis cluster to keep backups before they re deleted automatically you can specify from 1 to 365 days the default value is 35 days from the time window menu select a time for the daily backup in the maintenance section select one of the following options default memorystore for redis cluster updates your cluster routinely to ensure that the service is reliable performant secure and up to date custom you want to customize the maintenance schedule for your cluster to align with your application s needs and to minimize disruptions if you select this option then specify the day that you want maintenance to occur and the hour when you want the maintenance window to start click create cluster gcloud to create a single zone instance run the create command gcloud redis clusters create instance_id region region_id network network replica count replica_count node type node_type shard count shard_count zone distribution mode zone_distribution_mode zone zone replace the following instance_id is the id of the memorystore for redis cluster instance you re creating your instance id must be 1 to 63 characters and use only lowercase letters numbers or hyphens it must start with a lowercase letter and end with a lowercase letter or number region_id is the region where you want the instance placed network is the network used to create your instance it must use the format projects network_project_id global networks network_id the network id used here must match the network id used by the service connection policy otherwise the create operation fails replica_count is the number of replicas per shard accepted values are 0 5 node_type is the node type that you want to use for the cluster caution we recommend that you use the redis sh...