You can create, view, and monitor instances, manage networks and security policies, deliver data to data lakes, run 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 are performed at the instance level. You can create an instance by using the console, OpenAPI, or the Tablestore CLI.
View an instance
After you create an instance, you can view instance information in the Tablestore console.
Instance monitoring
In the Tablestore console, you can view monitoring data for an instance, such as requests per second, row count, traffic statistics, and CapacityUnits. For more information, see View monitoring data in the Tablestore console.
You can also monitor data for Tablestore instances using the Cloud Monitor console or an SDK. For more information, see View monitoring data using the Cloud Monitor console and an SDK.
Network management
Tablestore supports various network types to meet different network security requirements. For more information, see Network security management and Network ACL.
Security policies
To restrict access to an instance based on the source IP address, network, or TLS version, you can configure an instance policy to secure access sources. For more information, see Configure an instance policy and Instance policy permissions.
Data lake delivery
Tablestore data lake delivery performs full backups or delivers data in real time to an Object Storage Service (OSS) data lake for low-cost historical data storage and large-scale offline and near-real-time analytics.
SQL queries
SQL Query provides a unified access interface for the multiple data engines in Tablestore. It is compatible with MySQL syntax and suitable for online access to massive datasets. You can use SQL Query to run complex queries and perform efficient analysis on data in Tablestore.
Manage instance resources
If you have many Tablestore instances, you can use tags or resource groups to classify and manage them for automated O&M, access control, cost allocation, and resource monitoring.
Overdue payments, renewals, and upgrades
For information about the policies on overdue payments, renewals, and upgrades for Tablestore instances, see Overdue payments and service suspension.
Release an instance
If you no longer need an instance, you can release it to avoid incurring additional fees.