튜토리얼 ElasticSearch - TLS 암호화 및 HTTPS 사용

Elasticsearch TLS 암호화 및 HTTPS 통신을 활성화하는 방법을 알고 싶습니까? 이 자습서에서는 보안 기능을 활성화 하는 방법 및 우분투 리눅스를 실행 하는 컴퓨터에서 ElasticSearch 서버에 HTTPS 암호화를 사용 하는 방법을 보여 드리겠습니다.

• 우분투 18
• 우분투 19
• 탄성 검색 7.6.2
• 키바나 7.6.2

이 예제에서 ElastiSearch 서버 IP 주소는 192.168.100.7입니다.

ElasticSearch 관련 자습서:

이 페이지에서는 ElasticSearch 설치와 관련된 자습서 목록에 빠르게 액세스할 수 있습니다.

튜토리얼 ElasticSearch – 기본 라이센스 업그레이드

필요한 패키지를 설치합니다.

Copy to Clipboard

ElasticSearch 서버에 설치된 라이센스 유형을 확인합니다.

Copy to Clipboard

다음은 명령 출력입니다.

Copy to Clipboard

이 예제에서는 ElasticSearch 서버에 기본 라이센스가 설치되어 있습니다.

ElasticSearch 서버에서 평가판 라이선스를 활성화합니다.

Copy to Clipboard

ElasticSearch 기본 라이선스에서는 보안 기능을 사용할 수 없습니다.

튜토리얼 ElasticSearch – TLS 암호화 및 HTTPS 통신 을 활성화

ElasticSearch 서비스를 중지합니다.

Copy to Clipboard

자체 서명된 인증 기관을 만듭니다.

Copy to Clipboard

다음은 명령 출력입니다.

Copy to Clipboard

이 예제에서는 암호가 설정되지 않았습니다.

ElasticSearch 노드에 대한 인증서를 만듭니다.

Copy to Clipboard

다음은 명령 출력입니다.

Copy to Clipboard

This tool assists you in the generation of X.509 certificates and certificate
signing requests for use with SSL/TLS in the Elastic stack.

The 'cert' mode generates X.509 certificate and private keys.
    * By default, this generates a single certificate and key for use
       on a single instance.
    * The '-multiple' option will prompt you to enter details for multiple
       instances and will generate a certificate and key for each one
    * The '-in' option allows for the certificate generation to be automated by describing
       the details of each instance in a YAML file

* An instance is any piece of the Elastic Stack that requires an SSL certificate.
      Depending on your configuration, Elasticsearch, Logstash, Kibana, and Beats
      may all require a certificate and private key.
    * The minimum required value for each instance is a name. This can simply be the
      hostname, which will be used as the Common Name of the certificate. A full
      distinguished name may also be used.
    * A filename value may be required for each instance. This is necessary when the
      name would result in an invalid file or directory name. The name provided here
      is used as the directory name (within the zip) and the prefix for the key and
      certificate files. The filename is required if you are prompted and the name
      is not displayed in the prompt.
    * IP addresses and DNS names are optional. Multiple values can be specified as a
      comma separated string. If no IP addresses or DNS names are provided, you may
      disable hostname verification in your SSL configuration.

* All certificates generated by this tool will be signed by a certificate authority (CA).
    * The tool can automatically generate a new CA for you, or you can provide your own with the
         -ca or -ca-cert command line options.

By default the 'cert' mode produces a single PKCS#12 output file which holds:
    * The instance certificate
    * The private key for the instance certificate
    * The CA certificate

If you specify any of the following options:
    * -pem (PEM formatted output)
    * -keep-ca-key (retain generated CA key)
    * -multiple (generate multiple certificates)
    * -in (generate certificates from an input file)
then the output will be be a zip file containing individual certificate/key files

Enter password for CA (elastic-stack-ca.p12) :
Please enter the desired output file [elastic-certificates.p12]:
Enter password for elastic-certificates.p12 :

Certificates written to /usr/share/elasticsearch/elastic-certificates.p12

This file should be properly secured as it contains the private key for
your instance.

This file is a self contained file and can be copied and used 'as is'
For each Elastic product that you wish to configure, you should copy
this '.p12' file to the relevant configuration directory
and then follow the SSL configuration instructions in the product guide.

For client applications, you may only need to copy the CA certificate and
configure the client to trust this certificate.

이 예제에서는 암호가 설정되지 않았습니다.

인증서를 적절한 디렉터리로 복사하고 올바른 사용 권한을 설정합니다.

Copy to Clipboard

HTTPS 통신을 사용하도록 인증서를 만듭니다.

Copy to Clipboard

다음은 명령 출력입니다.

Copy to Clipboard

## Elasticsearch HTTP Certificate Utility

The 'http' command guides you through the process of generating certificates
for use on the HTTP (Rest) interface for Elasticsearch.

This tool will ask you a number of questions in order to generate the right
set of files for your needs.

## Do you wish to generate a Certificate Signing Request (CSR)?

A CSR is used when you want your certificate to be created by an existing
Certificate Authority (CA) that you do not control (that is, you don't have
access to the keys for that CA).

If you are in a corporate environment with a central security team, then you
may have an existing Corporate CA that can generate your certificate for you.
Infrastructure within your organisation may already be configured to trust this
CA, so it may be easier for clients to connect to Elasticsearch if you use a
CSR and send that request to the team that controls your CA.

If you choose not to generate a CSR, this tool will generate a new certificate
for you. That certificate will be signed by a CA under your control. This is a
quick and easy way to secure your cluster with TLS, but you will need to
configure all your clients to trust that custom CA.

Generate a CSR? [y/N]^C^Croot@elasticsearch:/etc/elasticsearch# ^C
root@elasticsearch:/etc/elasticsearch# vi /usr/share/elasticsearch/bin/elasticsearch-certutil
root@elasticsearch:/etc/elasticsearch# /usr/share/elasticsearch/bin/elasticsearch-certutil  http

## Elasticsearch HTTP Certificate Utility

The 'http' command guides you through the process of generating certificates
for use on the HTTP (Rest) interface for Elasticsearch.

This tool will ask you a number of questions in order to generate the right
set of files for your needs.

## Do you wish to generate a Certificate Signing Request (CSR)?

A CSR is used when you want your certificate to be created by an existing
Certificate Authority (CA) that you do not control (that is, you don't have
access to the keys for that CA).

If you are in a corporate environment with a central security team, then you
may have an existing Corporate CA that can generate your certificate for you.
Infrastructure within your organisation may already be configured to trust this
CA, so it may be easier for clients to connect to Elasticsearch if you use a
CSR and send that request to the team that controls your CA.

If you choose not to generate a CSR, this tool will generate a new certificate
for you. That certificate will be signed by a CA under your control. This is a
quick and easy way to secure your cluster with TLS, but you will need to
configure all your clients to trust that custom CA.

Generate a CSR? [y/N]

## Do you have an existing Certificate Authority (CA) key-pair that you wish to use to sign your certificate?

If you have an existing CA certificate and key, then you can use that CA to
sign your new http certificate. This allows you to use the same CA across
multiple Elasticsearch clusters which can make it easier to configure clients,
and may be easier for you to manage.

If you do not have an existing CA, one will be generated for you.

Use an existing CA? [y/N]y

## What is the path to your CA?

Please enter the full pathname to the Certificate Authority that you wish to
use for signing your new http certificate. This can be in PKCS#12 (.p12), JKS
(.jks) or PEM (.crt, .key, .pem) format.
CA Path: /usr/share/elasticsearch/elastic-stack-ca.p12
Reading a PKCS12 keystore requires a password.
It is possible for the keystore's password to be blank,
in which case you can simply press <ENTER> at the prompt
Password for elastic-stack-ca.p12:

## How long should your certificates be valid?

Every certificate has an expiry date. When the expiry date is reached clients
will stop trusting your certificate and TLS connections will fail.

Best practice suggests that you should either:
(a) set this to a short duration (90 - 120 days) and have automatic processes
to generate a new certificate before the old one expires, or
(b) set it to a longer duration (3 - 5 years) and then perform a manual update
a few months before it expires.

You may enter the validity period in years (e.g. 3Y), months (e.g. 18M), or days (e.g. 90D)

For how long should your certificate be valid? [5y]

## Do you wish to generate one certificate per node?

If you have multiple nodes in your cluster, then you may choose to generate a
separate certificate for each of these nodes. Each certificate will have its
own private key, and will be issued for a specific hostname or IP address.

Alternatively, you may wish to generate a single certificate that is valid
across all the hostnames or addresses in your cluster.

If all of your nodes will be accessed through a single domain
(e.g. node01.es.example.com, node02.es.example.com, etc) then you may find it
simpler to generate one certificate with a wildcard hostname (*.es.example.com)
and use that across all of your nodes.

However, if you do not have a common domain name, and you expect to add
additional nodes to your cluster in the future, then you should generate a
certificate per node so that you can more easily generate new certificates when
you provision new nodes.

Generate a certificate per node? [y/N]

## Which hostnames will be used to connect to your nodes?

These hostnames will be added as "DNS" names in the "Subject Alternative Name"
(SAN) field in your certificate.

You should list every hostname and variant that people will use to connect to
your cluster over http.
Do not list IP addresses here, you will be asked to enter them later.

If you wish to use a wildcard certificate (for example *.es.example.com) you
can enter that here.

Enter all the hostnames that you need, one per line.
When you are done, press <ENTER> once more to move on to the next step.

You did not enter any hostnames.
Clients are likely to encounter TLS hostname verification errors if they
connect to your cluster using a DNS name.

Is this correct [Y/n]

## Which IP addresses will be used to connect to your nodes?

If your clients will ever connect to your nodes by numeric IP address, then you
can list these as valid IP "Subject Alternative Name" (SAN) fields in your
certificate.

If you do not have fixed IP addresses, or not wish to support direct IP access
to your cluster then you can just press <ENTER> to skip this step.

Enter all the IP addresses that you need, one per line.
When you are done, press <ENTER> once more to move on to the next step.

You did not enter any IP addresses.

Is this correct [Y/n]

## Other certificate options

The generated certificate will have the following additional configuration
values. These values have been selected based on a combination of the
information you have provided above and secure defaults. You should not need to
change these values unless you have specific requirements.

Key Name: elasticsearch
Subject DN: CN=elasticsearch
Key Size: 2048

Do you wish to change any of these options? [y/N]

## What password do you want for your private key(s)?

Your private key(s) will be stored in a PKCS#12 keystore file named "http.p12".
This type of keystore is always password protected, but it is possible to use a
blank password.

If you wish to use a blank password, simply press <enter> at the prompt below.
Provide a password for the "http.p12" file:  [<ENTER> for none]

## Where should we save the generated files?

A number of files will be generated including your private key(s),
public certificate(s), and sample configuration options for Elastic Stack products.

These files will be included in a single zip archive.

What filename should be used for the output zip file? [/usr/share/elasticsearch/elasticsearch-ssl-http.zip]

Zip file written to /usr/share/elasticsearch/elasticsearch-ssl-http.zip

이 예제에서는 암호, DNS 및 IP 주소가 설정되지 않았습니다.

이 예제에서는 이전에 만든 자체 서명된 인증 기관을 사용했습니다.

인증서를 적절한 디렉터리로 복사하고 올바른 사용 권한을 설정합니다.

Copy to Clipboard

ElasticSearch 구성 파일 편집: elasticsearch.yml

Copy to Clipboard

파일 끝에 다음 줄을 추가합니다.

Copy to Clipboard

다음은 구성 전원본 파일입니다.

Copy to Clipboard

여기에 우리의 구성파일입니다.

Copy to Clipboard

ElasticSearch 서비스를 시작합니다.

Copy to Clipboard

ElasticSearch 기본 제공 사용자의 암호를 설정합니다.

Copy to Clipboard

다음은 명령 출력입니다.

Copy to Clipboard

ElasticSearch 서버와의 통신을 테스트합니다.

HTTPS를 사용해야 합니다.

따라서 가짜 인증서를 사용하고 있으므로 CURL 명령에서 인증서 확인을 비활성화해야 합니다.

Copy to Clipboard

다음은 명령 출력입니다.

Copy to Clipboard

ElasticSearch 서버에 사용자 인증이 필요합니다.

ELASTIC 사용자 계정을 사용하여 ElasticSearch 서버와의 통신을 테스트합니다.

Copy to Clipboard

다음은 명령 출력입니다.

Copy to Clipboard

명령줄에 사용자 암호를 입력하도록 선택할 수 있습니다.

Copy to Clipboard

축! ElasticSearch TLS 암호화 구성을 완료했습니다.

축! ElasticSearch HTTPS 구성을 완료했습니다.

튜토리얼 탄성 검색 – 키바나 구성

키바나 서비스를 중지합니다.

Copy to Clipboard

자체 서명된 인증 기관 인증서를 복사합니다.

Copy to Clipboard

키바나 구성 파일 편집: kibana.yml

Copy to Clipboard

탄력적 검색 연결을 HTTP에서 HTTPS로 찾아 변경합니다.

Copy to Clipboard

파일 끝에 다음 줄을 추가합니다.

Copy to Clipboard

다음은 구성 전원본 파일입니다.

Copy to Clipboard

여기에 우리의 구성파일입니다.

Copy to Clipboard

환경을 반영하도록 Kibana 암호를 변경해야 합니다.

키바나 서비스를 시작합니다.

Copy to Clipboard

브라우저를 열고 Kibana 서버의 IP 주소를 입력하고 :5601을 입력합니다.

이 예제에서는 브라우저에 다음 URL을 입력했습니다.

• http://192.168.100.7:5601

Kibana 웹 인터페이스를 제시해야 합니다.

로그인에 성공하면 Kibana 대시보드가 표시됩니다.

축! ElasticSearch에 대한 키바나 통합을 완료했습니다.

탄력적 검색 – TLS 암호화 및 HTTPS 통신 사용

탄력적 검색 – TLS 암호화 및 HTTPS 통신 사용

ElasticSearch 관련 자습서:

튜토리얼 ElasticSearch – 기본 라이센스 업그레이드

튜토리얼 ElasticSearch – TLS 암호화 및 HTTPS 통신 을 활성화

튜토리얼 탄성 검색 – 키바나 구성

탄력적 검색 – TLS 암호화 및 HTTPS 통신 사용

탄력적 검색 – TLS 암호화 및 HTTPS 통신 사용

ElasticSearch 관련 자습서:

튜토리얼 ElasticSearch – 기본 라이센스 업그레이드

튜토리얼 ElasticSearch – TLS 암호화 및 HTTPS 통신 을 활성화

튜토리얼 탄성 검색 – 키바나 구성

Related Posts