# Migration Connectivity Options

There are several connectivity options when migrating databases to the TiDB Cluster. The options are listed below in order of preference.

+ Private Endpoint:TiDB Cloud supports highly secure and one-way access to the TiDB Cloud service hosted in an AWS VPC via the AWS PrivateLink, as if the service were in your own VPC. A private endpoint is exposed in your VPC and you can create a connection to the TiDB Cloud service via the endpoint with permission. Private Endpoint can be use in both  Dedicated and Serverless Tier.
+ Standard connection:The standard connection exposes a public endpoint with traffic filters, so you can connect to your TiDB cluster via a SQL client from your laptop. Standard connection can be use in both  Dedicated and Serverless Tier.
+ VPC Peering: If you want lower latency and more security, set up VPC peering and connect via a private endpoint using a VM instance on the corresponding cloud provider in your cloud account. VPC Peering can be just used in Dedicated Tier.
+ SQL Shell:to try TiDB SQL and test out TiDB's compatibility with MySQL quickly, or administer user privileges. SQL Shell can be just used in Dedicated Tier.

-------------------------------------------------------------

+ Private Endpoint refers to https://docs.pingcap.com/tidbcloud/set-up-private-endpoint-connections
+ + Standard Connection refers to https://docs.pingcap.com/tidbcloud/connect-via-standard-connection#serverless-tier
VPC Peering refers to https://docs.pingcap.com/tidbcloud/set-up-vpc-peering-connections
+ SQL Shell refers to https://docs.pingcap.com/tidbcloud/connect-via-sql-shell