教程弹性搜索 - 启用 TLS 加密和 HTTPS

您想了解如何启用弹性搜索 TLS 加密和 HTTPS 通信吗？在本教程中，我们将向您展示如何启用安全功能以及如何在运行 Ubuntu Linux 的计算机上启用 ElasticSearch 服务器上的 HTTPS 加密。

• 乌本图 18
• 乌本图 19
• 弹性搜索 7.6.2
• 基巴纳 7.6.2

在我们的示例中，ElastiSearch 服务器 IP 地址为 192.168.100.7。

弹性搜索相关教程：

在此页上，我们提供快速访问与弹性搜索安装相关的教程列表。

教程弹性搜索 - 升级基本许可证

安装所需的软件包。

Copy to Clipboard

验证弹性搜索服务器上安装的许可证类型。

Copy to Clipboard

下面是命令输出。

Copy to Clipboard

在我们的示例中，我们在弹性搜索服务器上安装了基本许可证。

在弹性搜索服务器上启用试用许可证。

Copy to Clipboard

弹性搜索基本许可证上没有安全功能。

教程弹性搜索 - 启用 TLS 加密和 HTTPS 通信

停止弹性搜索服务。

Copy to Clipboard

创建自签名证书颁发机构。

Copy to Clipboard

下面是命令输出。

Copy to Clipboard

在我们的示例中，未设置密码。

为弹性搜索节点创建证书。

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

编辑名为：弹性搜索.yml 的弹性搜索配置文件

Copy to Clipboard

在文件末尾添加以下行。

Copy to Clipboard

这里是原始文件，在我们的配置之前。

Copy to Clipboard

下面是具有我们配置的文件。

Copy to Clipboard

启动弹性搜索服务。

Copy to Clipboard

设置弹性搜索内置用户的密码。

Copy to Clipboard

下面是命令输出。

Copy to Clipboard

测试您与弹性搜索服务器的通信。

请记住，我们需要使用 HTTPS。

请记住，我们使用的是假证书，因此，我们需要禁用 CURL 命令上的证书验证。

Copy to Clipboard

下面是命令输出。

Copy to Clipboard

弹性搜索服务器需要用户身份验证。

使用 ELASTIC 用户帐户测试您与弹性搜索服务器的通信。

Copy to Clipboard

下面是命令输出。

Copy to Clipboard

您可以选择在命令行上输入用户密码。

Copy to Clipboard

祝贺！您已完成弹性搜索 TLS 加密配置。

祝贺！您已完成弹性搜索 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

应显示基巴纳 Web 界面

成功登录后，应显示 Kibana 仪表板。

祝贺！您已完成基巴纳与弹性搜索的集成。

弹性搜索 - 启用 TLS 加密和 HTTPS 通信

弹性搜索 - 启用 TLS 加密和 HTTPS 通信

弹性搜索相关教程：

教程弹性搜索 - 升级基本许可证

教程弹性搜索 - 启用 TLS 加密和 HTTPS 通信

教程弹性搜索 - 基巴纳配置

Related Posts