This topic describes how to manage instances, such as how to create instances, view instances, monitor instances, manage networks, configure security policies, deliver data to Object Storage Service (OSS), perform SQL queries, release instances, and manage instance resources.
Create an instance
An instance is the basic unit of resource management in Tablestore. Access control and resource metering for applications in Tablestore are performed at the instance level. You can create an instance in the Tablestore console or by using OpenAPI Explorer or the Tablestore CLI. For more information, see Create an instance.
View instances
After you create an instance, you can view information of the instance in the Tablestore console. For more information, see View instances.
Monitor instances
You can view the monitoring data of Tablestore instances, such as queries per second (QPS), the number of rows, traffic statistics, and capacity units (CUs) in the Tablestore console. For more information, see View monitoring data in the Tablestore console.
You can view the monitoring data of Tablestore instances in the CloudMonitor console or by using CloudMonitor SDKs. For more information, see View monitoring data by using the CloudMonitor console and CloudMonitor SDKs.
Manage networks
Tablestore supports various combinations of network types to meet different network security requirements. For more information, see Network security management and Network ACL.
Configure security policies
Instance policies can be configured for a Tablestore instance to restrict the access sources of the instance by specifying allowed IP addresses, networks, and Transport Layer Security (TLS) versions. This ensures that only authorized access sources can access the instance and keeps the resources of the instance secure. For more information, see Use instance policies to restrict the access sources of an instance and Configure an instance policy.
Deliver data to OSS
Tablestore uses data delivery to deliver full or incremental data to Object Storage Service (OSS) in real time. This way, historical data can be stored at low costs and offline or quasi-real-time analysis of large amounts of data can be performed. For more information, see Data delivery.
Perform SQL queries
The SQL query feature provides a centralized access interface for multiple data engines of Tablestore and is compatible with the query syntax of MySQL. The SQL query feature is suitable for scenarios in which a large volume of data is stored and you want to access the data online. You can use the SQL query feature to perform complex queries and analytics on data in Tablestore in an efficient manner. For more information, see SQL query.
Manage instance resources
If you have a large number of Tablestore instances, you can use tags or resource groups to classify and manage the instances. For example, you can automate O&M, control resource access, manage ledgers, and monitor resources by tag.
Overdue payments, renewals, and upgrades
For information about the overdue payment, renewal, and upgrade policies of Tablestore instances, see Overdue payments and service suspension.
Release instances
If you no longer require an instance, you can release the instance to prevent unnecessary costs.