Console

1. In the Google Cloud console, go to the Create instance page.

   Go to Create instance

2. Enter a name for the instance.

   The Google Cloud console displays this name to identify your instance.

3. Enter an instance ID.

   The instance ID is a permanent identifier for the instance.

4. Click Continue.

5. Choose whether to use an SSD or HDD disk for your clusters. In most cases, SSD is best. This choice is permanent. Learn more.

6. Click Continue.

7. Enter a cluster ID for the first cluster.

   The cluster ID is a permanent identifier for the cluster.

8. Choose the region and zone where the first cluster will run.

9. Optional: To configure the cluster to always scale in increments of two nodes, select Enable 2x node scaling. 2x node scaling is not available in all zones. For more information, see Node scaling factor.

10. Choose a node scaling mode for the cluster. In most cases, you should choose autoscaling. For scaling guidance, see Autoscaling.

    1. For Manual node allocation, enter the number of Bigtable nodes for the first cluster. If you aren't sure how many nodes you need, use the default. You can add more nodes later.
    2. For Autoscaling, enter values for the following:
       • Minimum number of nodes
       • Maximum number of nodes
       • CPU utilization target
       • Storage utilization target

11. Optional: To protect your instance with CMEK instead of the default Google-managed encryption, complete the following:

    1. Click Show encryption options.
    2. Select Cloud KMS key.
    3. In the Key management type field, select one of the following options:
       • If you want to automate creation of Cloud KMS keys, select Cloud KMS with Autokey, and then click Request a key. A message indicates when your key has been successfully created and is ready for use.
       • If you want to add a key manually, select Cloud KMS. Select or enter the resource name for the CMEK key that you want to use for the cluster. You cannot add this later. If you are prompted to grant permission to the CMEK key's service account, click Grant. Your user account must be granted the Cloud KMS Admin role to complete this task. Click Save.

12. Optional: To enable replication now, complete the following additional steps:

    1. Click Show advanced options.
    2. Click Add cluster, enter the settings for the cluster, and then click Add. Repeat this step to create additional clusters in the instance. You can also enable replication later by adding a cluster.

    Each zone in a region can contain only one cluster. If the Add cluster button is disabled, change the zone for your first cluster.

    To create an instance that has more than six clusters, first create an instance that has six clusters, then add more clusters to the instance.

13. Click Create to create the instance.

14. Review the replication settings in the default app profile to see if they make sense for your replication use case. You might need to update the default app profile or create custom app profiles.

gcloud

1. Use the bigtable instances create command to create an instance:

   gcloud bigtable instances create INSTANCE_ID \
       --display-name=DISPLAY_NAME \
       [--cluster-storage-type=CLUSTER_STORAGE_TYPE] \
       [--cluster-config=id=CLUSTER_ID,zone=CLUSTER_ZONE, \
       nodes=NODES] \
       [--cluster-config=id=CLUSTER_ID,zone=CLUSTER_ZONE, \
       autoscaling-min-nodes=AUTOSCALING_MIN_NODES, \
       autoscaling-max-nodes=AUTOSCALING_MAX_NODES, \
       autoscaling-cpu-target=AUTOSCALING_CPU_TARGET, \
       autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET, \
       kms-key=KMS_KEY], \
       [node-scaling-factor=NODE_SCALING_FACTOR]
   

   Replace the following:

   • INSTANCE_ID: The permanent identifier for the instance.
   • DISPLAY_NAME: A human-readable name that identifies the instance in the Google Cloud console.
   • CLUSTER_ID: The permanent identifier for the cluster.
   • CLUSTER_ZONE: The zone where the cluster runs.

   You must configure at least one cluster for the instance, using the --cluster-config flag. To create an instance that has multiple clusters, repeat the --cluster-config flag for each cluster.

   For manual node allocation, setting nodes in the --cluster-config flag is optional. If no value is set, Bigtable allocates nodes to the cluster automatically based on your data footprint and optimizes for 50% storage utilization. This automatic allocation of nodes has a pricing impact. If you want to control the number of nodes in a cluster, replace NODES with the number of nodes that you want in the cluster. Learn more about nodes.

   In most cases, choose autoscaling instead of manual node allocation. For_autoscaling, provide autoscaling- options in the --cluster-config flag (autoscaling-storage-target is optional) and don't use nodes. See Autoscaling for guidance on choosing the values for your autoscaling settings. Replace the following for the cluster-config option keys:

   • AUTOSCALING_MIN_NODES: The minimum number of nodes for the cluster.
   • AUTOSCALING_MAX_NODES: The maximum number of nodes for the cluster.
   • AUTOSCALING_CPU_TARGET: The target CPU utilization percentage for the cluster. This value must be from 10 to 80.
   • AUTOSCALING_STORAGE_TARGET: (Optional) The storage utilization target in GiB that Bigtable maintains by adding or removing nodes.

   • KMS_KEY: The CMEK key for the cluster.

     The KMS_KEY value must be set in the following format:

     projects/PROJECT/locations/LOCATION/keyRings/KEYRING/cryptoKeys/KEY
     
     

     Replace the following:

     • PROJECT: the permanent identifier for the project
     • LOCATION: the location of your cluster
     • KEYRING: the name of the key ring that contains the key
     • KEY: the name of the key

     The following is an example:

     projects/examplestore.com:dev/locations/us-east1/keyRings/devt-cmek-2/cryptoKeys/key2

     If the instance is CMEK-protected, each cluster must be in the same region as its CMEK key. You can add CMEK clusters only to instances that are already CMEK-protected. Learn more.

   The command accepts the following optional flags:

   • --cluster-storage-type=CLUSTER_STORAGE_TYPE: The type of storage to use for the instance. The default value is SSD. In most cases, the default value is best. This choice is permanent. Learn more.

   • --project=PROJECT: The project in which to create the cluster if different from the current project.

   • node-scaling-factor=NODE_SCALING_FACTOR: A flag that enables 2x node scaling. You can enable this feature with both manual scaling and autoscaling. Acceptable values are node-scaling-factor-2x or node-scaling-factor-1x.

   To view a list of Bigtable zones that aren't available for 2x node scaling, see Node scaling factor limitations.

2. Review the replication settings in the default app profile to see if they make sense for your replication use case. You might need to update the default app profile or create custom app profiles.

cbt

1. Start by creating an instance with a single cluster. Use the createinstance command to create an instance:

   cbt createinstance INSTANCE_ID \
       DISPLAY_NAME \
       CLUSTER_ID \
       CLUSTER_ZONE \
       CLUSTER_NUM_NODES \
       CLUSTER_STORAGE_TYPE
   

   Provide the following:

   • INSTANCE_ID: The permanent identifier for the instance.
   • DISPLAY_NAME: A human-readable name that identifies the instance in the Google Cloud console.
   • CLUSTER_ID: The permanent identifier for the cluster.
   • CLUSTER_ZONE: The zone where the cluster runs.
   • CLUSTER_NUM_NODES: This field is optional. If no value is set, Bigtable automatically allocates nodes based on your data footprint and optimizes for 50% storage utilization. If you want to control the number of nodes in a cluster, update the CLUSTER_NUM_NODES value. Ensure that number of nodes is set to a non-zero value. Learn more about nodes.
   • CLUSTER_STORAGE_TYPE: The type of storage to use for the cluster. Each cluster in an instance must use the same storage type. Accepts the values SSD and HDD. In most cases, SSD is best. This choice is permanent. Learn more.

2. To enable replication, use the createcluster command to add a cluster:

   
   cbt -instance=INSTANCE_ID \
   createcluster CLUSTER_ID \
   ZONE \
   NUM_NODES \
   STORAGE_TYPE
   
   

   Provide the following:

   • INSTANCE_ID: The permanent identifier for the instance you just created.
   • CLUSTER_ID: The permanent identifier for the cluster.

   • ZONE: The zone where the cluster runs.

     Each zone in a region can contain only one cluster. For example, if an instance has a cluster in us-east1-b, you can add a cluster in a different zone in the same region, such as us-east1-c, or a zone in a separate region, such as europe-west2-a.

   • NUM_NODES: This field is optional. If no value is set, Bigtable automatically allocates nodes based on your data footprint and optimizes for 50% storage utilization. If you want to control the number of nodes in a cluster, update the NUM_NODES value. Ensure that number of nodes is set to a non-zero value.

     In many cases, each cluster in an instance should have the same number of nodes, but there are exceptions. Learn about nodes and replication.

   • STORAGE_TYPE: The type of storage to use for the cluster. Each cluster in an instance must use the same storage type. Accepts the values SSD and HDD.

3. (Optional) Review the replication settings in the default app profile to see if they make sense for your replication use case. You might need to update the default app profile or create custom app profiles.

C++

C#

Java

Node.js

PHP

Python

Ruby