A Cloud Bigtable instance is a container for a single Cloud Bigtable cluster. The instance ID and cluster ID combine to uniquely identify your cluster.
When you create your Cloud Bigtable instance, take note of the instance ID. You'll need this value to connect to your instance.
- Go to the Google Cloud Platform Console.
- Create a new GCP Console project, or open an existing project by selecting the project name. ...see naming guidelines
- Enable the Cloud Bigtable and Cloud Bigtable Admin APIs.
To create a Cloud Bigtable instance:
Create a new instance in the GCP Console.
Enter a name for the instance. The name is used to identify your instance in the GCP Console.
- Enter an instance ID. The instance ID is a permanent identifier for your instance that is unique within your Cloud Platform project.
Select which type of instance to create.
- Production: A high-availability instance with three or more nodes. You cannot downgrade a production instance to a development instance.
- Development: A low-cost instance with performance limited to the equivalent of a single node. It is typically used for development and testing. There are no monitoring or throughput guarantees, and the SLA does not apply. You can upgrade a development instance to a production instance at any time.
Enter a cluster ID. The cluster ID is a permanent identifier for your cluster that is unique within your instance.
- Choose the zone where your Cloud Bigtable cluster will run. Use the same zone you use for other Cloud Platform services, or another zone in the same region.
- Choose the number of Cloud Bigtable nodes for your cluster. You can change this value later.
Choose whether to use an SSD or HDD disk for your cluster. In most cases, SSD is the best choice. Your choice is permanent. See "Choosing between SSD and HDD storage" for details.
The GCP Console shows you how the disk type and number of nodes affect the number of queries per second (QPS) and megabytes per second (MB/s) your cluster can handle, as well as the cost for your cluster.
Click Create to create the instance.
To create a Cloud Bigtable instance:
Install the Cloud SDK if you haven't already.
beta bigtable instances createcommand to create an instance:
gcloud beta bigtable instances create INSTANCE --cluster=CLUSTER \ --cluster-zone=CLUSTER_ZONE \ [--instance-type=INSTANCE_TYPE; default="PRODUCTION"] [--cluster-num-nodes=CLUSTER_NUM_NODES] \ --description=DESCRIPTION [--async] \ [--cluster-storage-type=CLUSTER_STORAGE_TYPE; default="SSD"] \
INSTANCE: Is the permanent identifier for your instance.
CLUSTER: Is the permanent identifier for your cluster.
CLUSTER_ZONE: Is the zone where your Cloud Bigtable cluster runs.
DESCRIPTION: Is a human-readable name for the instance.
The command accepts the following optional flags:
--instance-type=INSTANCE_TYPE: The type of instance to create. Accepts one of the following values:
PRODUCTION(default): A high-availability instance with three or more nodes. You cannot downgrade a production instance to a development instance.
DEVELOPMENT: A low-cost instance with performance limited to the equivalent of a single node. It is typically used for development and testing. There are no monitoring or throughput guarantees, and the SLA does not apply. You can upgrade a development instance to a production instance at any time.
--cluster-num-nodes=CLUSTER_NUM_NODES: The size of the Cloud Bigtable cluster. A production instance must have three or more nodes. Do not use this flag for development instances.
--async: Return immediately without waiting for the operation to finish.
--cluster-storage-type=CLUSTER_STORAGE_TYPE: The type of storage to use for the cluster. Accepts the values