* NEW [conf] add tls config to nanomq_briege.conf.
@@ -107,6 +107,54 @@ bridge.mqtt.aws.subscription.2.qos=2
## Value: 1-infinity
bridge.mqtt.aws.parallel=2
+## enable tls
+##
+## Value: true | false
+bridge.mqtt.aws.tls.enable=false
+
+## tls key password
+## String containing the user's password. Only used if the private keyfile
+## is password-protected.
+##
+## Value: String
+## bridge.mqtt.aws.tls.key_password=yourpass
+
+## tls keyfile
+## Path of the file containing the client's private key.
+##
+## Value: File
+bridge.mqtt.aws.tls.keyfile=/etc/certs/key.pem
+
+## tls cert file
+## Path of the file containing the client certificate.
+##
+## Value: File
+bridge.mqtt.aws.tls.certfile=/etc/certs/cert.pem
+
+## tls ca cert file
+## Path of the file containing the server's root CA certificate.
+##
+## This certificate is used to identify the AWS IoT server and is publicly
+## available.
+##
+## Value: File
+bridge.mqtt.aws.tls.cacertfile=/etc/certs/cacert.pem
+
+## A server only does x509-path validation in mode verify_peer,
+## as it then sends a certificate request to the client (this
+## message is not sent if the verify option is verify_none).
+## You can then also want to specify option fail_if_no_peer_cert.
+##
+## Value: true: verify_peer | false: verify_none
+bridge.mqtt.aws.tls.verify_peer=false
+
+## Used together with {verify, verify_peer} by an SSL server. If set to true,
+## the server fails if the client does not have a certificate to send, that is,
+## sends an empty certificate.
+##
+## Value: true | false
+bridge.mqtt.aws.tls.fail_if_no_peer_cert=false
+
##--------------------------------------------------------------------
## Next bridge configuration
