MySQL over SSH

This provisions a new MySQL database in an existing MySQL instance. The Driver will first connect to an SSH server acting as a bastion host and then port forward to the MySQL instance. The SSH server must be accessible from Humanitec IPs and the MySQL instance must be directly accessible from the SSH server.

Property Description
Resource type mysql
Account type None

Inputs

Values

Name Type Description
host string The IP Address or hostname that the instance is available on.
port integer The port the instance is listening on.
append_host_to_user boolean [Optional] Azure Databases for Postgres and MySQL require usernames to have @servername appended to them. Set this to true for the Driver to append this automatically. (See: Azure Database connection strings)
copy_from_name string [Optional] If provided, specifies the database in the same instance to copy data from.
ssh_host string Hostname or IP address of the SSH server.
ssh_port integer The port to connect to on the SSH server.
ssh_user string The username to use to connect to the SSH server.

Secrets

Name Type Description
dbcredentials object An object holding username and password properties for the PostgreSQL superuser.

Notes

Configuring the SSH server

In order for the Driver to use the SSH server as a bastion host, the following needs to be configured:

  • The Humanitec Database Server Public Key must be added to the authorized_keys file on the server.
  • The user that is used for connecting on must have permissions to perform a port forward.
  • The SSH server must be configured to allow port forwarding - typically via an entry in the configuration file similar to AllowTcpForwarding yes

The Humanitec Database Server Public Key is:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDun1ycsXCKX3LyzoZjpzFuWtUoonq/8j6gmtWJObgyiYtustJt7uiEJtrTuaObAf/ys1isolrCHQ748Psbhxz3d7T+kHlqto5j3E42CwP8G92bPpYz3EKWGPn1GyAmnoqBHTVau6XwIe8TBh5zCWsaxe/nkxP3Dcd17f/TBnnVxDar6OvOLJ4nmNToJNvYMQdrxsLTVmBGFPDQz8N/wstgdI47K2g/cW+brvkZaoVCsUxDfzw8iQk5v+vx4GD6+puFJjFh7RXa1XrsbM+utoQET7g6wntk54RCNSdunV+JX9RhRdeYwyGteyFaacl6Xb3Y8uZRNbLMSuostr+P/v7f [email protected]

Automatic population of database

MySQL does not provide any standard way of duplicating databases. Instead, the suggested approach is to “dump and restore” a database using tools such as mysqldump.

This Driver emulates a dump and restore of the database: for example, it serially copies data from the source database to the target database. It therefore suffers from limitations of dumping and restoring a database. The main issue is that if the source database is being written to, there are no guarantees about the data integrity in the resulting database. Consider a source database with 2 tables A and B:

  1. Table A is copied to the target database.
  2. New data is then written to Table A and Table B in the source database.
  3. Table B is copied from the source database to the target database.

The target database will now have the updated to table B but not table A.

This capability should not be used for production databases or where data integrity must be guaranteed.

Example

To create a fresh MySQL database in an instance available at dev-mysql.internal.example.com accessed via a bastion host on bastion.example.com as the user example-ssh-user:

curl https://api.humanitec.io/orgs/${HUMANITEC_ORG}/resources/defs \
  -X POST \
  -H "Authorization: Bearer ${HUMANITEC_TOKEN}" \
  -H "Content-Type: application/json" \
  --data-binary '
{
  "id": "dev-mysql",
  "name": "Dev MySQL",
  "type": "mysql",
  "criteria": [
    {
      "env_type": "development"
    }
  ],
  "driver_type": "humanitec/mysql-ssh",
  "driver_inputs": {
    "values": {
      "host": "dev-mysql.example.com",
      "port": 3306,
      "ssh_host": "bastion.example.com",
      "ssh_port": 22,
      "ssh_user": "example-ssh-user"
    },
    "secrets": {
      "dbcredentials": {
        "username": "root",
        "password": "53cr3t-P455w0rd"
      }
    }
  }
}'

Most MySQL implementations use a single shared Driver. For Google MySQL implementations, see the Google MySQL Driver.

Prerequisites

  • You must have a database instance/server running.
  • If you are using a hosted MySQL it is recommended provide a management service account with Database CRUD permissions. You will need to add this account via the Cloud Accounts screen.
  • You must have a user defined on the instance for Workloads to use when connecting to the database.

Add a Resource Definition

  1. From the Resource Management screen, click Add resource definition.
  2. In the modal dialog click MySQL.
  3. Next, select the mysql-cloudsql Driver.
  4. Finally, provide the following information, then click Add Postgress.
    1. In the ID field provide a unique ID for the resource.
    2. (If you are using a management account) in the Credentials field select the Cloud Account you created earlier.
    3. In the Fully qualified CloudSQL instance name provide the instance name in the format <project-id>:<region>:<id>.
    4. In the User / Role and Password fields provide the credentials that Workloads should use when connecting to the database.
    5. In the Hostname or IP field provide the Hostname or IP address that the Workloads can access the database on.
    6. In the Port field provide the port number that the database is running on.

Resource Matching

Now that the resource is defined you will need to add matching criteria.

  1. Click on the relevant row in the Resource Definition table.
  2. Then switch to the Matching Criteria tab.
  3. Click + Add new Criteria.
  4. Configure the matching rules as needed.
  5. Click Save.

MySQL Cloud SQL

PostgreSQL