셀프 호스팅 MySQL 또는 MariaDB를 사용한 데이터베이스 접근

요약

Teleport can provide secure access to MySQL or MariaDB via the Teleport Database Service. The Teleport Database Service proxies traffic from database clients to self-hosted databases in your infrastructure.

Teleport can provide secure access to MySQL or MariaDB via the Teleport Database Service. This allows for fine-grained access control through the Teleport RBAC system.

The Teleport Database Service proxies traffic from database clients to self-hosted databases in your infrastructure. Teleport maintains a certificate authority (CA) for database clients. You configure your database to trust the Teleport database client CA, and the Teleport Database Service presents certificates signed by this CA when proxying user traffic. With this setup, there is no need to store long-lived credentials for self-hosted databases.

Meanwhile, the Teleport Database Service verifies self-hosted databases by checking their TLS certificates against either the Teleport database CA or a custom CA used with the database.

In this guide, you will:

Configure your MySQL or MariaDB database for Teleport access.
Add the database to your Teleport cluster.
Connect to the database via Teleport.

작동 방식#

The Teleport Database Service authenticates to your self-hosted MySQL or MariaDB database using mutual TLS. MySQL or MariaDB trusts the Teleport certificate authority for database clients, and presents a certificate signed by either the Teleport database CA or a custom CA. When a user initiates a database session, the Teleport Database Service presents a certificate signed by Teleport. The authenticated connection then proxies client traffic from the user.

셀프 호스팅 Teleport 클러스터로 MySQL 등록

클라우드 호스팅 Teleport 클러스터로 MySQL 등록

사전 조건#

A running Teleport cluster. If you want to get started with Teleport, sign up for a free trial or set up a demo environment.
The tctl and tsh clients.
Installing `tctl` and `tsh` clients
1. Determine the version of your Teleport cluster. The tctl and tsh clients must be at most one major version behind your Teleport cluster version. Send a GET request to the Proxy Service at /v1/webapi/find and use a JSON query tool to obtain your cluster version. Replace with the web address of your Teleport Proxy Service:
```
$ TELEPORT_DOMAIN=
$ TELEPORT_VERSION="$(curl -s https://$TELEPORT_DOMAIN/v1/webapi/find | jq -r '.server_version')"
```
2. Follow the instructions for your platform to install tctl and tsh clients:

셀프 호스팅 MySQL 또는 MariaDB 인스턴스.
Teleport 데이터베이스 서비스를 실행할 호스트(예: Amazon EC2 인스턴스).
선택 사항: 셀프 호스팅 데이터베이스에 대한 인증서를 발급하는 인증 기관.

To check that you can connect to your Teleport cluster, sign in with tsh login, then verify that you can run tctl commands using your current credentials.

For example, run the following command, assigning to the domain name of the Teleport Proxy Service in your cluster and to your Teleport username:

$ tsh login --proxy= --user=
$ tctl status
# Cluster  (=teleport.url=)
# Version  (=teleport.version=)
# CA pin   (=presets.ca_pin=)

If you can connect to the cluster and run the tctl status command, you can use your current credentials to run subsequent tctl commands from your workstation. If you host your own Teleport cluster, you can also run tctl commands on the computer that hosts the Teleport Auth Service for full permissions.

1/4단계. Teleport 데이터베이스 토큰 생성#

The Database Service requires a valid join token to join your Teleport cluster. Run the following tctl command and save the token output in /tmp/token on the server that will run the Database Service:

$ tctl tokens add --type=db --format=text
(=presets.tokens.first=)

2/4단계. 인증서/키 쌍 생성#

Teleport uses mutual TLS authentication with self-hosted databases. These databases must be able to verify certificates presented by the Teleport Database Service. Self-hosted databases also need a certificate/key pair that Teleport can verify.

By default, the Teleport Database Service trusts certificates issued by a certificate authority managed by the Teleport Auth Service. You can either:

Configure your self-hosted database to trust this CA, and instruct Teleport to issue a certificate for the database to present to the Teleport Database Service.
Configure the Database Service to trust a custom CA.

3/4단계. MySQL/MariaDB 구성#

MySQL이 TLS 연결을 수락하도록 구성하려면 MySQL 구성 파일 mysql.cnf에 다음을 추가합니다:

[mysqld]
require_secure_transport=ON
ssl-ca=/path/to/server.cas
ssl-cert=/path/to/server.crt
ssl-key=/path/to/server.key

MariaDB가 TLS 연결을 수락하도록 구성하려면 MariaDB 구성 파일 mysql.cnf에 다음을 추가합니다:

[mariadb]
require_secure_transport=ON
ssl-ca=/path/to/server.cas
ssl-cert=/path/to/server.crt
ssl-key=/path/to/server.key

이 구성을 활성화하려면 데이터베이스 인스턴스를 재시작합니다. 또한 MySQL/MariaDB 데이터베이스 사용자 계정은 유효한 클라이언트 인증서를 요구하도록 구성되어야 합니다.

새 사용자를 생성합니다:

CREATE USER 'alice'@'%' REQUIRE SUBJECT '/CN=alice';

기본적으로 생성된 사용자는 아무것에도 접근할 수 없어 연결할 수 없으므로 일부 권한을 부여합니다:

GRANT ALL ON `%`.* TO 'alice'@'%';

Warning

이것은 사용자에게 데이터베이스 전체 권한을 부여하는 예시 명령입니다. 프로덕션 환경에서는 최소 권한 원칙을 따라야 합니다.

Teleport는 인증서를 사용하여 데이터베이스 사용자를 인증하므로, 해당 사용자에게 패스워드가 설정되어 있으면 안 됩니다. 기존 사용자의 패스워드를 제거하면 기존 통합이 중단될 수 있습니다. Teleport 접근을 위해 전용 새 데이터베이스 사용자를 사용하는 것을 고려하세요.

유효한 인증서를 요구하도록 기존 사용자를 업데이트합니다:

ALTER USER 'alice'@'%' REQUIRE SUBJECT '/CN=alice';

사용자에서 패스워드를 제거합니다:

SET PASSWORD FOR 'alice'@'%' = PASSWORD("");

자세한 내용은 MySQL 문서의 암호화된 연결 사용을 위한 MySQL 구성 또는 MariaDB 문서의 MariaDB 서버에서 TLS 활성화를 참조하세요.

Teleport 사용자 생성#

Flag	Description
`--roles`	List of roles to assign to the user. The builtin `access` role allows them to connect to any database server registered with Teleport.
`--db-users`	List of database usernames the user will be allowed to use when connecting to the databases. A wildcard allows any user.
`--db-names`	List of logical databases (aka schemas) the user will be allowed to connect to within a database server. A wildcard allows any database.

For more detailed information about database access controls and how to restrict access see RBAC documentation.

데이터베이스 서비스 구성 및 시작#

Teleport 데이터베이스 서비스를 실행할 위치에 Teleport를 설치하고 구성합니다:

To install a Teleport Agent on your Linux server:

The recommended installation method is the cluster install script. It will select the correct version, edition, and installation mode for your cluster.

Assign to your Teleport cluster hostname and port, but not the scheme (https://).

Run your cluster's install script:

$ curl "https:///scripts/install.sh" | sudo bash

On the host where you will run the Teleport Database Service, start Teleport with the appropriate configuration.

Note that a single Teleport process can run multiple different services, for example multiple Database Service agents as well as the SSH Service or Application Service. The step below will overwrite an existing configuration file, so if you're running multiple services add --output=stdout to print the config in your terminal, and manually adjust /etc/teleport.yaml.

Run the following command to generate a configuration file at /etc/teleport.yaml for the Database Service. Update to use the host and port of the Teleport Proxy Service:

$ sudo teleport db configure create \
   -o file \
   --token=/tmp/token \
   --proxy=:443 \
   --name=example-mysql \
   --protocol=mysql \
   --uri=mysql.example.com:3306 \
   --labels=env=dev

To configure the Teleport Database Service to trust a custom CA:

Export a CA certificate for the custom CA and make it available at /var/lib/teleport/db.ca on the Teleport Database Service host.

Run a variation of the command above that uses the --ca-cert-file flag. This configures the Teleport Database Service to use the CA certificate at db.ca to verify traffic from the database:

$ sudo teleport db configure create \
   -o file \
   --token=/tmp/token \
   --proxy=:443 \
   --name=example-mysql \
   --protocol=mysql \
   --uri=mysql.example.com:3306 \
   --ca-cert-file="/var/lib/teleport/db.ca" \
   --labels=env=dev

If your database servers use certificates that are signed by a public CA such as ComodoCA or DigiCert, you can use the trust-system-cert-pool option without exporting the CA:

$ sudo teleport db configure create \
   -o file \
   --token=/tmp/token \
   --proxy=:443 \
   --name=example-mysql \
   --protocol=mysql \
   --uri=mysql.example.com:3306 \
   --trust-system-cert-pool \
   --labels=env=dev

(!docs/pages/includes/start-teleport.mdx service="the Teleport Database Service"!)

Teleport는 Kubernetes 클러스터에 Teleport 데이터베이스 서비스를 설치하기 위한 Helm 차트를 제공합니다.

Configure Helm to fetch Teleport charts from the Teleport Helm repository:

$ helm repo add teleport (=teleport.helm_repo_url=)

Refresh the local Helm cache by fetching the latest charts:

$ helm repo update

Install a Teleport Agent into your Kubernetes Cluster with the Teleport Database Service configuration.

Create a file called values.yaml with the following content. Update

데이터베이스에서 로그아웃하고 자격 증명을 제거하려면:

# 특정 데이터베이스 인스턴스의 자격 증명 제거.
$ tsh db logout example-mysql
# 모든 데이터베이스 인스턴스의 자격 증명 제거.
$ tsh db logout

셀프 호스팅 MySQL 또는 MariaDB를 사용한 데이터베이스 접근

원문 보기

번역일: 2026-05-14

요약

Teleport can provide secure access to MySQL or MariaDB via the Teleport Database Service. This allows for fine-grained access control through the Teleport RBAC system.

Meanwhile, the Teleport Database Service verifies self-hosted databases by checking their TLS certificates against either the Teleport database CA or a custom CA used with the database.

In this guide, you will:

Configure your MySQL or MariaDB database for Teleport access.
Add the database to your Teleport cluster.
Connect to the database via Teleport.

작동 방식#

셀프 호스팅 Teleport 클러스터로 MySQL 등록

클라우드 호스팅 Teleport 클러스터로 MySQL 등록

사전 조건#

A running Teleport cluster. If you want to get started with Teleport, sign up for a free trial or set up a demo environment.
The tctl and tsh clients.
Installing `tctl` and `tsh` clients
1. Determine the version of your Teleport cluster. The tctl and tsh clients must be at most one major version behind your Teleport cluster version. Send a GET request to the Proxy Service at /v1/webapi/find and use a JSON query tool to obtain your cluster version. Replace with the web address of your Teleport Proxy Service:
```
$ TELEPORT_DOMAIN=
$ TELEPORT_VERSION="$(curl -s https://$TELEPORT_DOMAIN/v1/webapi/find | jq -r '.server_version')"
```
2. Follow the instructions for your platform to install tctl and tsh clients:

셀프 호스팅 MySQL 또는 MariaDB 인스턴스.
Teleport 데이터베이스 서비스를 실행할 호스트(예: Amazon EC2 인스턴스).
선택 사항: 셀프 호스팅 데이터베이스에 대한 인증서를 발급하는 인증 기관.

To check that you can connect to your Teleport cluster, sign in with tsh login, then verify that you can run tctl commands using your current credentials.

For example, run the following command, assigning to the domain name of the Teleport Proxy Service in your cluster and to your Teleport username:

$ tsh login --proxy= --user=
$ tctl status
# Cluster  (=teleport.url=)
# Version  (=teleport.version=)
# CA pin   (=presets.ca_pin=)

1/4단계. Teleport 데이터베이스 토큰 생성#

$ tctl tokens add --type=db --format=text
(=presets.tokens.first=)

2/4단계. 인증서/키 쌍 생성#

By default, the Teleport Database Service trusts certificates issued by a certificate authority managed by the Teleport Auth Service. You can either:

Configure your self-hosted database to trust this CA, and instruct Teleport to issue a certificate for the database to present to the Teleport Database Service.
Configure the Database Service to trust a custom CA.

3/4단계. MySQL/MariaDB 구성#

MySQL이 TLS 연결을 수락하도록 구성하려면 MySQL 구성 파일 mysql.cnf에 다음을 추가합니다:

[mysqld]
require_secure_transport=ON
ssl-ca=/path/to/server.cas
ssl-cert=/path/to/server.crt
ssl-key=/path/to/server.key

MariaDB가 TLS 연결을 수락하도록 구성하려면 MariaDB 구성 파일 mysql.cnf에 다음을 추가합니다:

[mariadb]
require_secure_transport=ON
ssl-ca=/path/to/server.cas
ssl-cert=/path/to/server.crt
ssl-key=/path/to/server.key

새 사용자를 생성합니다:

CREATE USER 'alice'@'%' REQUIRE SUBJECT '/CN=alice';

기본적으로 생성된 사용자는 아무것에도 접근할 수 없어 연결할 수 없으므로 일부 권한을 부여합니다:

GRANT ALL ON `%`.* TO 'alice'@'%';

Warning

이것은 사용자에게 데이터베이스 전체 권한을 부여하는 예시 명령입니다. 프로덕션 환경에서는 최소 권한 원칙을 따라야 합니다.

유효한 인증서를 요구하도록 기존 사용자를 업데이트합니다:

ALTER USER 'alice'@'%' REQUIRE SUBJECT '/CN=alice';

사용자에서 패스워드를 제거합니다:

SET PASSWORD FOR 'alice'@'%' = PASSWORD("");

자세한 내용은 MySQL 문서의 암호화된 연결 사용을 위한 MySQL 구성 또는 MariaDB 문서의 MariaDB 서버에서 TLS 활성화를 참조하세요.

Teleport 사용자 생성#

Flag	Description
`--roles`	List of roles to assign to the user. The builtin `access` role allows them to connect to any database server registered with Teleport.
`--db-users`	List of database usernames the user will be allowed to use when connecting to the databases. A wildcard allows any user.
`--db-names`	List of logical databases (aka schemas) the user will be allowed to connect to within a database server. A wildcard allows any database.

For more detailed information about database access controls and how to restrict access see RBAC documentation.

데이터베이스 서비스 구성 및 시작#

Teleport 데이터베이스 서비스를 실행할 위치에 Teleport를 설치하고 구성합니다:

To install a Teleport Agent on your Linux server:

The recommended installation method is the cluster install script. It will select the correct version, edition, and installation mode for your cluster.

Assign to your Teleport cluster hostname and port, but not the scheme (https://).

Run your cluster's install script:

$ curl "https:///scripts/install.sh" | sudo bash

On the host where you will run the Teleport Database Service, start Teleport with the appropriate configuration.

Run the following command to generate a configuration file at /etc/teleport.yaml for the Database Service. Update to use the host and port of the Teleport Proxy Service:

$ sudo teleport db configure create \
   -o file \
   --token=/tmp/token \
   --proxy=:443 \
   --name=example-mysql \
   --protocol=mysql \
   --uri=mysql.example.com:3306 \
   --labels=env=dev

To configure the Teleport Database Service to trust a custom CA:

Export a CA certificate for the custom CA and make it available at /var/lib/teleport/db.ca on the Teleport Database Service host.

Run a variation of the command above that uses the --ca-cert-file flag. This configures the Teleport Database Service to use the CA certificate at db.ca to verify traffic from the database:

$ sudo teleport db configure create \
   -o file \
   --token=/tmp/token \
   --proxy=:443 \
   --name=example-mysql \
   --protocol=mysql \
   --uri=mysql.example.com:3306 \
   --ca-cert-file="/var/lib/teleport/db.ca" \
   --labels=env=dev

If your database servers use certificates that are signed by a public CA such as ComodoCA or DigiCert, you can use the trust-system-cert-pool option without exporting the CA:

$ sudo teleport db configure create \
   -o file \
   --token=/tmp/token \
   --proxy=:443 \
   --name=example-mysql \
   --protocol=mysql \
   --uri=mysql.example.com:3306 \
   --trust-system-cert-pool \
   --labels=env=dev

(!docs/pages/includes/start-teleport.mdx service="the Teleport Database Service"!)

Teleport는 Kubernetes 클러스터에 Teleport 데이터베이스 서비스를 설치하기 위한 Helm 차트를 제공합니다.

Configure Helm to fetch Teleport charts from the Teleport Helm repository:

$ helm repo add teleport (=teleport.helm_repo_url=)

Refresh the local Helm cache by fetching the latest charts:

$ helm repo update

Install a Teleport Agent into your Kubernetes Cluster with the Teleport Database Service configuration.

Create a file called values.yaml with the following content. Update

데이터베이스에서 로그아웃하고 자격 증명을 제거하려면:

# 특정 데이터베이스 인스턴스의 자격 증명 제거.
$ tsh db logout example-mysql
# 모든 데이터베이스 인스턴스의 자격 증명 제거.
$ tsh db logout