If you don't have SSH configured, then you've been using the secure hypertext transfer protocol (HTTPS) to communicate between your local system and Bitbucket Cloud. Set up SSH to reduce the risk of exposing your username and password.
This table compares HTTPS and SSH to give you a better idea of the difference between the two.
Is suitable if you push to and pull from Bitbucket infrequently.
Requires you to enter a password each time you connect.
Is more effective if you push and pull from Bitbucket many times a day.
Removes the need to enter a password each time you connect.
The URL you use to access a repository depends on the connection protocol (HTTPS or SSH) and the distributed version control system. You can find your repository-specific URLs from the repository Source page. The following table shows these URL formats:
Bitbucket supports four encryption algorithms for user keys: Ed25519, ECDSA, RSA, and DSA. Create keys using the encryption method that is available to you.
You may want to record Bitbucket's public host key before connecting to it for the first time. Depending on the security protocols in your network, the system administrator may maintain a centrally located list of approved known hosts. The public key fingerprints for the Bitbucket server are: