add some english readme

Author: yaopengbo

elkeidup/README.md

@@ -13,7 +13,7 @@ Automated deployment of Elkeid tools
 * The back-end server used for deployment needs to ensure intranet interoperability
 * The backend server used for deployment requires root user privileges when deploying
 * The backend server used for deployment can only be used: Centos7 and above; Ubuntu16 and above; Debian9 and above
-* The server which execute elkeidup could execute ssh root@x.x.x.x without password to any backend server
+* The server which execute elkeidup could execute `ssh root@x.x.x.x` without password to any backend server
 * Deployment cannot be manually interrupted
 * Only cat use LAN IP, do not use 127.0.0.1 or hostname or public IP
 * Don't remove `~/.elkeidup` dir

elkeidup/deploy-zh_CN.md

@@ -157,4 +157,4 @@ cd /root/.elkeidup
 ko/sign文件的格式应该遵循：`hids_driver_1.7.0.4_{uname -r}_{arch}.ko/sign`格式， 文件需要放置在nginx对应服务器的：`/elkeid/nginx/ElkeidAgent/agent/component/driver/ko`下，并修改权限`chown -R nginx:nginx /elkeid/nginx`。放置完成后，重启Agent即可。
 
 ## 4、HTTPS配置
-请参考[Elkeid https配置文档](./https_config/https.md)
+请参考[Elkeid https配置文档](./https_config/https-zh_CN.md)

elkeidup/deploy_hub-zh_CN.md

@@ -50,4 +50,4 @@ cd /root/.elkeidup
 访问 elkeid_hub_frontend，参照 [Elkeid HUB 社区版快速上手教程](https://github.com/bytedance/Elkeid-HUB/blob/main/docs/quick_start/quick_start.md) 使用。
 
 ## 6、HTTPS配置
-请参考[Elkeid https配置文档](./https_config/https.md)
+请参考[Elkeid https配置文档](./https_config/https-zh_CN.md)

elkeidup/deploy_hub.md

@@ -15,19 +15,20 @@ wget https://github.com/bytedance/Elkeid/releases/download/v1.9.1/elkeidup_hub_v
 chmod a+x /root/.elkeidup/elkeidup
 ```
 ### 3、Generate and modify config.yaml
-If it is not a standalone deployment, please refer to the deployment resource manual to modify config.yaml
-ip为本机非 `127.0.0.1` ip，若不为单机部署，请参考[部署资源手册](./configuration-zh_CN.md)修改config.yaml
+If it is not a standalone deployment, please refer to the [deployment resource manual](./configuration.md) to modify config.yaml
+
 ```
 cd /root/.elkeidup
-## 生成hub only 配置
+## Generate hub only configurations
 ./elkeidup init --host {ip} --hub_only
 mv config_example.yaml config.yaml
 ```
-### 4、部署
+
+### 4、Deployment
 ```
 cd /root/.elkeidup
 
-# 命令为交互式
+# Command is interactive
 ./elkeidup deploy --hub_only
 
 ## status
@@ -37,18 +38,18 @@ cd /root/.elkeidup
 ./elkeidup undeploy --hub_only
 ```
 
-### 5、访问HUB前端
-顺利安装完成后，执行`cat /root/.elkeidup/elkeid_passwd`将看到各组件的随机生成的密码和相关的url。
+### 5、Visit the HUB front end
+After a successful installation, executing `cat /root/.elkeidup/elkeid_passwd` will see the randomly generated passwords and associated URLs for each component.
 
-| 字段                         | 说明               |
+| Field | Description |
 | -------------------------- |------------------|
-| elkeid_hub_frontend        | hub前端账号密码        |
-| grafana        | grafana账号密码      |
-| grafana      | grafana 地址       |
-| elkeid_hub_frontend      | elkeid hub前端地址   |
-| elkeid_service_discovery | 服务发现地址           |
+| elkeid_hub_frontend | hub front-end account password |
+| grafana | grafana account password |
+| grafana | grafana address |
+| elkeid_hub_frontend | elkeid hub front-end address |
+| elkeid_service_discovery | Service Discovery Address |
 
-访问 elkeid_hub_frontend，参照 [Elkeid HUB 社区版快速上手教程](https://github.com/bytedance/Elkeid-HUB/blob/main/docs/quick_start/quick_start.md) 使用。
+To access elkeid_hub_frontend, refer to the [Elkeid HUB Quick Start Tutorial](https://github.com/bytedance/Elkeid-HUB/blob/main/docs/quick_start/quick_start.md).
 
-## 6、HTTPS配置
-请参考[Elkeid https配置文档](./https_config/https.md)
+## 6、HTTPS configuration
+Please refer to [Elkeid https configuration documentation](./https_config/https.md)

elkeidup/https_config/https-zh_CN.md

@@ -0,0 +1,39 @@
+# Elkeid https配置文档
+
+## 1 概述
+- 默认情况下，Elkeid Console监听在8082和8072端口，Elkeid HUB监听在8081和8071端口。
+- 如果需要使用HTTPS，可以使用8072和8071端口来访问。
+
+|       | Elkeid Console           | Elkeid HUB Console       |
+|-------|--------------------------|--------------------------|
+| HTTP  | http://{{NignxIP}}:8082  | http://{{NignxIP}}:8081  |
+| HTTPS | https://{{NignxIP}}:8072 | https://{{NignxIP}}:8072 |
+
+## 2、使用企业内部证书
+安装时生成的自签名证书位于nginx所在机器的 `/elkeid/nginx/nginx` 目录，包括以下两个文件：
+```
+server.key
+server.crt
+```
+替换上述两个文件后，执行以下操作即可：
+```
+chown -R nginx:nginx /elkeid/nginx
+systemctl restart elkeid_nginx
+```
+
+## 3、使用部署时生成的自签名证书
+Elkeid 在部署时，仅能使用自签名证书，由于chrome的安全设置，无法直接访问，所有需要手动信任该证书才可使用https访问，具体操作参考如下：
+以下示例假设nginx所在服务器为 `console.elkeid.org`，并配置了`/etc/hosts`或dns解析。
+### 3.1、Macos
+1. 访问 `https://console.elkeid.org:8072/`  导出证书
+   ![cert1](001.png)
+   ![cert2](002.png)
+2. 导入导出的证书并信任
+   ![cert3](003.png)
+   ![cert4](004.png)
+   ![cert5](005.png)
+3. 点击钥匙串访问，信任证书
+   ![cert6](006.png)
+4. 再次访问 `https://console.elkeid.org:8072/`
+   ![cert7](007.png)
+   ![cert8](008.png)

elkeidup/https_config/https.md

@@ -1,39 +1,39 @@
-# Elkeid https配置文档
+# Elkeid https configuration documentation
 
-## 1 概述
-- 默认情况下，Elkeid Console监听在8082和8072端口，Elkeid HUB监听在8081和8071端口。
-- 如果需要使用HTTPS，可以使用8072和8071端口来访问。
+## 1. Overview
+- By default, the Elkeid Console listens on ports 8082 and 8072, and the Elkeid HUB listens on ports 8081 and 8071.
+- If HTTPS is required, ports 8072 and 8071 can be used for access.
 
 |       | Elkeid Console           | Elkeid HUB Console       |
 |-------|--------------------------|--------------------------|
 | HTTP  | http://{{NignxIP}}:8082  | http://{{NignxIP}}:8081  |
 | HTTPS | https://{{NignxIP}}:8072 | https://{{NignxIP}}:8072 |
 
-## 2、使用企业内部证书
-安装时生成的自签名证书位于nginx所在机器的 `/elkeid/nginx/nginx` 目录，包括以下两个文件：
+## 2. Use an internal enterprise certificate
+The self-signed certificate generated during installation is located in the '/elkeid/nginx/nginx' directory on the machine where nginx is located, and includes the following two files:
 ```
 server.key
 server.crt
 ```
-替换上述两个文件后，执行以下操作即可：
+After replacing the above two files, do the following:
 ```
-chown -R nginx:nginx /elkeid/nginx
+chown -R nginx: nginx /elkeid/nginx
 systemctl restart elkeid_nginx
 ```
 
-## 3、使用部署时生成的自签名证书
-Elkeid 在部署时，仅能使用自签名证书，由于chrome的安全设置，无法直接访问，所有需要手动信任该证书才可使用https访问，具体操作参考如下：
-以下示例假设nginx所在服务器为 `console.elkeid.org`，并配置了`/etc/hosts`或dns解析。
-### 3.1、Macos
-1. 访问 `https://console.elkeid.org:8072/`  导出证书
+## 3. Use the self-signed certificate generated at deployment time
+When Elkeid is deployed, it can only use a self-signed certificate. Due to the security settings of chrome, it cannot be accessed directly. All you need to manually trust the certificate to access it using https. The specific operation is as follows:
+The following example hypotheses that the server where nginx is located is `console.elkeid.org` and has a configuration of `/etc/hosts` or dns parsing.
+### 3.1, Macos
+1. Access https://console.elkeid.org:8072/ Export Certificate
    ![cert1](001.png)
    ![cert2](002.png)
-2. 导入导出的证书并信任
+2. Import the exported certificate and trust it
    ![cert3](003.png)
    ![cert4](004.png)
    ![cert5](005.png)
-3. 点击钥匙串访问，信任证书
+3. Click Keychain Access, Trust Certificate
    ![cert6](006.png)
-4. 再次访问 `https://console.elkeid.org:8072/`
+4. Visit https://console.elkeid.org:8072/ again
    ![cert7](007.png)
    ![cert8](008.png)