Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

InfluxDB Enterprise: Recommend one certificate per node (#3066)

pull/3069/head
pierwill 2021-08-26 10:56:08 -05:00 committed by GitHub
parent 41f3b1f6e6
commit f6bedb4d25
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/enterprise_influxdb/v1.8/guides/https_setup.md
View File

@ -51,6 +51,8 @@ Regardless of your certificate's type, InfluxDB Enterprise supports certificates
a private key file (`.key`) and a signed certificate file (`.crt`) file pair, as well as certificates
that combine the private key file and the signed certificate file into a single bundled file (`.pem`).
In general, each node node should have its own certificate, whether signed or unsiged.
## Set up HTTPS in an InfluxDB Enterprise cluster
1. **Download or generate certificate files**

2
content/enterprise_influxdb/v1.9/guides/https_setup.md
View File

@ -51,6 +51,8 @@ Regardless of your certificate's type, InfluxDB Enterprise supports certificates
a private key file (`.key`) and a signed certificate file (`.crt`) file pair, as well as certificates
that combine the private key file and the signed certificate file into a single bundled file (`.pem`).
In general, each node node should have its own certificate, whether signed or unsiged.
## Set up HTTPS in an InfluxDB Enterprise cluster
1. **Download or generate certificate files**