Connect to your YugabyteDB database from your desktop using the YugabyteDB [ysqlsh](../../../api/ysqlsh/) and [ycqlsh](../../../api/ycqlsh/) client shells. Because YugabyteDB is compatible with PostgreSQL and Cassandra, you can also use [psql](https://www.postgresql.org/docs/15/app-psql.html) and third-party tools to connect. You can connect to the database on a universe in the following ways: - Use SSH to tunnel to one of the universe nodes, and run ysqlsh or ycqlsh on the node. - Download and run the client shells from your desktop. ## Download the universe certificate If the universe uses Client-to-Node encryption in transit, to connect you need to first download the universe TLS certificate. Do the following: 1. Navigate to **Integrations > Security > Encryption in Transit**. 1. Find your universe in the list. 1. Click **Actions** and choose **Download Root CA Cert**. This downloads the `root.crt` file. For information on connecting using a client shell using this certificate, see [Connect from your desktop](#connect-from-your-desktop). To use TLS to connect an application, refer to the [driver documentation](/stable/develop/drivers-orms/). If you are using a PostgreSQL JDBC driver to connect to YugabyteDB, you can also refer to [Configuring the client](https://jdbc.postgresql.org/documentation/head/ssl-client.html) for more details. If you are using PostgreSQL/YugabyteDB JDBC driver with SSL, you need to convert the certificates to DER format. To do this, you need to perform only steps 6 and 7 from [Set up SSL certificates for Java applications](/stable/develop/drivers-orms/java/postgres-jdbc-reference/#set-up-ssl-certificates-for-java-applications) section after downloading the certificates. ## Connect to a universe node The YugabyteDB shells are installed in the tserver/bin directory on each YB-TServer of a YugabyteDB universe. ### Access your YugabyteDB Anywhere instance To connect to a universe node, you first need to be signed on to the machine where YugabyteDB Anywhere is installed, or connected via SSH. To SSH to a YugabyteDB Anywhere instance hosted on the cloud provider, you enter the following: ```sh ssh -i username@ ``` For example, for an AWS instance, you can SSH using a command similar to the following: ```sh ssh -i ~/.yugabyte/yb-dev-aws-2.pem ec2-user@my.yugabyte.aws ``` If your instance is on Kubernetes, use kubectl commands to connect. For example: ```sh gcloud container clusters get-credentials --region us-west1 itest-release --project yugabyte kubectl exec -it yw-ns-kvik-id7973-20230213-031611-yugaware-0 -n yw-ns-kvik-id7973-20230213-031611 -c yugaware -- bash ``` ### Connect to a node To run a shell from a universe node, do the following: 1. In YugabyteDB Anywhere, navigate to your universe and select the **Nodes** tab. ![Multi-zone universe nodes](/images/yp/multi-zone-universe-nodes-1.png) 1. Determine the node to which you wish to connect and click **Actions > Connect**. 1. Copy the SSH command displayed in the **Access your node** dialog shown in the following illustration: ![Multi-zone universe connect](/images/yp/multi-zone-universe-connect-2.png) 1. From the machine where YugabyteDB Anywhere is installed, run the command you copied. For example: ```sh.output sudo ssh -i /opt/yugabyte/yugaware/data/keys/f000ad00-aafe-4a67-bd1f-34bdaf3bee00/yb-dev-yugabyte-google-provider_f033ad00-aafe-4a00-bd1f-34bdaf3bee00-key.pem -ostricthostkeychecking=no -p 22 yugabyte@ Are you sure you want to continue connecting (yes/no)? yes [ec2-user@yb-dev-helloworld1-n1 ~]$ ``` 1. On the node, navigate to the tserver/bin directory: ```sh cd /home/yugabyte/tserver/bin ``` 1. Run ysqlsh or ycqlsh as follows: ```sh ./ysqlsh -h ``` ```sh ./ycqlsh ``` ### Enable Tectia SSH By default, YugabyteDB Anywhere uses OpenSSH for SSH to remote nodes. YugabyteDB Anywhere also supports the use of Tectia SSH that is based on the latest SSH G3 protocol. [Tectia SSH](https://www.ssh.com/products/tectia-ssh/) is used for secure file transfer, secure remote access and tunnelling. YugabyteDB Anywhere is shipped with a trial version of Tectia SSH client that requires a license to notify YugabyteDB Anywhere to permanently use Tectia instead of OpenSSH. To upload the Tectia license, manually copy it at `${storage_path}/yugaware/data/licenses/`, where _storage_path_ is the path provided during installation. After the license is uploaded, YugabyteDB Anywhere exposes the runtime flag `yb.security.ssh2_enabled` that you need to enable, as per the following example: ```shell curl --location --request PUT 'http:///api/v1/customers//runtime_config/00000000-0000-0000-0000-000000000000/key/yb.security.ssh2_enabled' --header 'Cookie: ' --header 'X-AUTH-TOKEN: ' --header 'Csrf-Token: ' --header 'Content-Type: text/plain' --data-raw '"true"' ``` ## Connect from your desktop ### Prerequisites - If you are using [ysqlsh](../../../api/ysqlsh/) or [ycqlsh](../../../api/ycqlsh/), ensure you are running the latest versions of the shells. - If your universe has Client-to-Node encryption in transit enabled, you need to [download the certificate](#download-the-universe-certificate) to your computer. - The host address of an endpoint on your universe. To view your universe endpoints, navigate to your universe and click **Connect**. ### Connect using a client shell Use the ysqlsh, ycqlsh, and psql shells to connect to and interact with YugabyteDB using the YSQL and YCQL APIs.
To connect using ysqlsh, use the following connection string: ```sh ./ysqlsh "host= \ user= \ dbname=yugabyte \ sslmode=verify-full \ sslrootcert=" ``` Replace the following: - `` with the IP address of an endpoint on your universe. - `` with your database username. - `yugabyte` with the database name, if you're connecting to a database other than the default (yugabyte). - `` with the path to the universe root certificate you downloaded to your computer. To load sample data and explore an example using ysqlsh, follow the instructions in [Install the Retail Analytics sample database](../../../sample-data/retail-analytics/#install-the-retail-analytics-sample-database).
To connect using ycqlsh, use the following connection string: ```sh SSL_CERTFILE= \ ./ycqlsh \ 9042 \ -u \ --ssl ``` Replace the following: - `` with the IP address of an endpoint on your universe. - `` with your database username. - `` with the path to the universe root certificate you downloaded to your computer.
To connect using [psql](https://www.postgresql.org/docs/15/app-psql.html), use the following connection string: ```sh ./psql --host= --port=5433 \ --username= \ --dbname=yugabyte \ --set=sslmode=verify-full \ --set=sslrootcert= ``` Replace the following: - `` with the IP address of an endpoint on your universe. - `` with your database username. - `yugabyte` with the database name, if you're connecting to a database other than the default (yugabyte). - `` with the path to the universe root certificate you downloaded to your computer.
### Connect using third party clients Because YugabyteDB is compatible with PostgreSQL and Cassandra, you can use third-party clients to connect to your YugabyteDB clusters in YugabyteDB Aeon. To connect, follow the client's configuration steps for PostgreSQL or Cassandra, and use the following values: - **host** address of an endpoint on your universe. - **port** 5433 for YSQL, 9042 for YCQL. - **database** name; the default YSQL database is yugabyte. - **username** and **password** of a user with permissions for the database; the default admin user is `yugabyte` (YSQL) or `cassandra` (YCQL). Your client may also require the use of the [universe certificate](#download-the-universe-certificate). For information on using popular third-party tools with YugabyteDB, see [Third party tools](/stable/integrations/tools/). ## Run workloads YugabyteDB Anywhere includes a number of sample applications provided in Docker containers. To run sample applications on your universe, do the following: 1. [Connect to a universe node](#connect-to-a-universe-node). 1. Navigate to your universe and click **Actions > Run Sample Apps** to open the **Run Sample Apps** dialog shown in the following illustration: ![Run sample apps](/images/yp/multi-zone-universe-sample-apps-1.png) 1. Run the suggested Docker command in your SSH session on the node. The **Metrics** tab of the universe allows you to see the metrics graphs, where server-side metrics tally with the client-side metrics reported by the load tester. You can also view metrics at a per-node level. You can stop the load tester as follows: - Find the container by executing the following command: ```shell user@yugaware-1:~$ sudo docker container ls | grep "yugabytedb/yb-sample-apps" ``` Expect an output similar to the following: ```output yugabytedb/yb-sample-apps "/usr/bin/java -jar …" 17 seconds ago Up 16 seconds jovial_morse ``` For example, if the container ID is ac144a49d57d, you would see the following output: ```output ac144a49d57d yugabytedb/yb-sample-apps "/usr/bin/java -jar …" 17 seconds ago Up 16 seconds jovial_morse ``` - Stop the container by executing the following command: ```shell user@yugaware-1:~$ sudo docker container stop ``` Expect the following output: ```output ``` For example, for a container with ID ac144a49d57d, you would need to execute the following command: ```shell user@yugaware-1:~$ sudo docker container stop ac144a49d57d ``` You would see the following output: ```output ac144a49d57d ``` ### Examine data Connect to the YCQL service by executing the following command: ```sh /home/yugabyte/tserver/bin/ycqlsh ``` You can view the table schema and the data, as follows: ```sql ycqlsh> DESCRIBE ybdemo_keyspace.cassandrakeyvalue; ``` ```output.cql CREATE TABLE ybdemo_keyspace.cassandrakeyvalue ( k text PRIMARY KEY, v blob ) WITH default_time_to_live = 0; ``` ```sql ycqlsh> SELECT * FROM ybdemo_keyspace.cassandrakeyvalue LIMIT 5; ``` ```output k | v ------------+----------------------------------------- key:101323 | 0x4276616c3a3130313332336be1dd6597e2... key:159968 | 0x4276616c3a3135393936381ed99587c08f... key:24879 | 0x4276616c3a3234383739054071b34c3fb6... key:294799 | 0x4276616c3a3239343739398b312748e80e... key:297045 | 0x4276616c3a32393730343525764eedee94... (5 rows) ``` ## Learn more - [Securing YugabyteDB: Client-to-Server Encryption in Transit](https://www.yugabyte.com/blog/securing-yugabytedb-client-to-server-encryption/#verification-of-server-certificates) - [ysqlsh](../../../api/ysqlsh/) — Overview of the command line interface (CLI), syntax, and commands. - [YSQL API](../../../api/ysql/) — Reference for supported YSQL statements, data types, functions, and operators. - [ycqlsh](../../../api/ycqlsh/) — Overview of the command line interface (CLI), syntax, and commands. - [YCQL API](../../../api/ycql/) — Reference for supported YCQL statements, data types, functions, and operators.