Elasticsearch를 사용한 데이터베이스 접근

요약

Teleport can provide secure access to Elasticsearch 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 Elasticsearch 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 Elasticsearch 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 Elasticsearch database using mutual TLS. Elasticsearch 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.

사전 조건#

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:

셀프 호스팅 Elasticsearch 데이터베이스. Elastic Cloud는 데이터베이스 서비스 설정에 필요한 클라이언트 인증서를 지원하지 않습니다.
Teleport 데이터베이스 서비스를 실행할 호스트.

자세한 내용은 설치를 참조하세요.
선택 사항: 셀프 호스팅 데이터베이스에 대한 인증서를 발급하는 인증 기관.

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/5단계. 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=)

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=myelastic \
   --protocol=elastic \
   --uri=elasticsearch.example.com:9200 \
   --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=myelastic \
   --protocol=elastic \
   --uri=elasticsearch.example.com:9200 \
   --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=myelastic \
   --protocol=elastic \
   --uri=elasticsearch.example.com:9200 \
   --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

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.

3/5단계. 역할 매핑 생성#

Elasticsearch에서 역할 매핑을 정의하여 Teleport 사용자 또는 역할을 Elasticsearch 역할에 할당합니다. 아래 예시는 Teleport 사용자 alice를 Elasticsearch의 user 역할에 매핑합니다.

$ curl -u elastic:your_elasticsearch_password -X POST "https://elasticsearch.example.com:9200/_security/role_mapping/mapping1?pretty" -H 'Content-Type: application/json' -d'
{
  "roles": [ "user"],
  "enabled": true,
  "rules": {
    "field" : { "username" : "alice" }
  },
  "metadata" : {
    "version" : 1
  }
}
'

와일드카드를 사용한 역할 매핑

Teleport가 싱글 사인온을 사용하는 시나리오에서는 모든 사용자를 역할에 매핑하도록 정의할 수 있습니다:

$ curl -u elastic:your_elasticsearch_password -X POST "https://elasticsearch.example.com:9200/_security/role_mapping/mapping1?pretty" -H 'Content-Type: application/json' -d'
{
  "roles": [ "monitoring"],
  "enabled": true,
  "rules": {
    "field" : { "username" : "*@example.com" }
  },
  "metadata" : {
    "version" : 1
  }
}
'

4/5단계. 상호 TLS 설정#

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.

생성된 시크릿을 사용하여 elasticsearch.yml 구성 파일에서 상호 TLS를 활성화합니다:

xpack.security.http.ssl:
  certificate_authorities: /path/to/server.cas
  certificate: /path/to/server.crt
  key: /path/to/server.key
  enabled: true
  client_authentication: required
  verification_mode: certificate

xpack.security.authc.realms.pki.pki1:
  order: 1
  enabled: true
  certificate_authorities: /path/to/server.cas

이 구성을 활성화하려면 Elasticsearch를 재시작합니다. 상호 TLS가 활성화되면 유효한 클라이언트 인증서 없이는 클러스터에 연결할 수 없습니다. xpack.security.http.ssl.client_authentication을 optional로 설정하면 인증서를 제시하지 않는 클라이언트가 사용자 이름 및 패스워드와 같은 다른 방법을 사용하여 연결할 수 있습니다.

5/5단계. 연결#

Teleport 클러스터에 로그인하고 사용 가능한 데이터베이스를 확인합니다:

$ tsh login --proxy=teleport.example.com --user=alice
$ tsh db ls
Name                        Description Allowed Users Labels  Connect
--------------------------- ----------- ------------- ------- ------------------------
> myelastic (user: elastic)             [*]           env=dev tsh db connect myelastic

$ tsh login --proxy=mytenant.teleport.sh --user=alice
$ tsh db ls
Name                        Description Allowed Users Labels  Connect
--------------------------- ----------- ------------- ------- ------------------------
> myelastic (user: elastic)             [*]           env=dev tsh db connect myelastic

특정 데이터베이스 인스턴스에 연결하려면:

$ tsh db connect myelastic --db-user=alice

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

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

터널 연결 예시#

Elasticvue와 같은 GUI 애플리케이션과 함께 사용할 수 있는 Elasticsearch에 대한 터널 연결을 생성할 수 있습니다:

$ tsh proxy db myelastic --db-user=alice --tunnel
Started authenticated tunnel for the Elasticsearch database "myelastic" in cluster "teleport.example.com" on 127.0.0.1:53657.

Use one of the following commands to connect to the database:

  * interactive SQL connection:

  $ elasticsearch-sql-cli http://localhost:53657/

  * run single request with curl:

  $ curl http://localhost:53657/

할당된 포트를 확인하고 GUI 클라이언트에 제공합니다:

ElasticVue

다음 단계#

Learn how to restrict access to certain users and databases.
View the High Availability (HA) guide.
Take a look at the YAML configuration reference.
See the full CLI reference.

Elasticsearch에서 보안 설정 구성에 대한 자세한 내용은 다음을 참조하세요: Elasticsearch의 보안 설정